Failed to create mountpoint

[rogerh]

Well, you need to fee up at least 100MB or so before you can do anything with mountpoints, datasets, etc.

So first you need to delete something so the zpool isn't locked up like it currently is. ;)

There was a whole thread on this, and how to do this without using unavailable zfs resources, but I can't find it! OTOH, if the OP can sacrifice a whole dataset, will "zfs destroy" work in this situation?

 

[cyberjock]

There was a whole thread on this, and how to do this without using unavailable zfs resources, but I can't find it! OTOH, if the OP can sacrifice a whole dataset, will "zfs destroy" work in this situation?

Nope. Can't destroy a dataset, or even delete a file. Gotta zero out a file with the echo command. That has to come first. ;)

 

[Zurlox]

Ok so this command "echo > /path/to/file/you/want/to/delete"

Taken from https://forums.freenas.org/index.php?threads/disk-full-cant-delete-any-files-please-help.12252/

I'll try this

 

[Zurlox]

Trying to zero a file results in 'No such file of directory'

I am trying to zero a known file from withing /mnt/Vault/Misc/Programs/

I type 'echo > /mnt/Vault/Misc/Programs/filename.end'

This returns the above error

 

[cyberjock]

Is Misc or Programs a dataset?

 

[rogerh]

What does "ls -l /mnt/Vault/Misc/Programs/<filename.end> show? By all means edit the actual filename to show us.

 

[Zurlox]

Yeah Misc is a dataset within the Vault pool

writing ls -l to the directory gives the below error

 

[rogerh]

Yeah Misc is a dataset within the Vault pool

writing ls -l to the directory gives the below error
View attachment 8830

Does that apply to all the files you could use, or does ls actually show any suitable files if you use ls without the filename, or in a different directory? If it finds one, I'd suggest using its path in the echo command.

 

[Zurlox]

I can use the ls command in /mnt/Vault but not in any of the datasets within Vault, so /mnt/Vault/Misc doesn't work, /mnt/Vault/Movies, etc ..

Might be in the position of dumping the lot and starting fresh...

 

[rogerh]

I can use the ls command in /mnt/Vault but not in any of the datasets within Vault, so /mnt/Vault/Misc doesn't work, /mnt/Vault/Movies, etc ..

Might be in the position of dumping the lot and starting fresh...

I have no idea if ls should work on a full ZFS filesystem, but if it doesn't I'm not sure why 'echo' does. In the absence of any expert advice I have no idea what to do next. Are you sure you've got the capitalisation correct on your file path? That's the only thing I can think of, assuming the file is still there!

 

[SweetAndLow]

You need to do d a file that actually exists. Use ls to find a file on your filesystem and use that path/file with the echo command.

 

[rogerh]

You need to do d a file that actually exists. Use ls to find a file on your filesystem and use that path/file with the echo command.

He says that ls shows nothing below his top-level datasets in the pool. Is this because ls doesn't work in a full pool or something more sinister?

 

[Ericloewe]

Could be a dataset and folder with the same name. Easily fixable with a working pool. On a full pool, I have no idea how to approach the issue.

 

[rogerh]

Could be a dataset and folder with the same name. Easily fixable with a working pool. On a full pool, I have no idea how to approach the issue.

That seems unlikely to have happened to all his top level datasets. @Zurlox, what about "ls /mnt/Vault/.freenas/' ?

 

[Zurlox]

Ok ls /mnt/Vaunt/.freenas/ returns the following screen


ls /mnt/Vault/ returns the following screen


Thanks guys, I really do appreciate your continued assistance.

 

[rogerh]

Ok ls /mnt/Vaunt/.freenas/ returns the following screen
View attachment 8832

ls /mnt/Vault/ returns the following screen
View attachment 8833

Thanks guys, I really do appreciate your continued assistance.

At this point I am totally mystified. The only directory you can access is .freenas which, if mine is anything to go by, contains no significant size files. The other contents of /mnt/Vault look like a home directory. I have no idea how it got like that, or how to find a file to delete. I think around this point I would give up hope of getting to the pool! There is nothing else unexpected in "ls /mnt/" I suppose?

 

[Zurlox]

That's alright. I have wiped and recreated my volume.

Also set up cron jobs for config integrity testing and backup.

Thanks for all your help :)

 

[Apollo]

Just curious to see if this post could have helped solve your issue:

https://forums.freenas.org/index.php?threads/cannot-mount-file-name-too-long.38470/

Also, it may not be possible deleting files within the dataset as mounting may not be possible, however I think it should still be possible to delete some snaphots, which in the process should release enough blocks making mounting possible based on the findings on my post mentioned above.
just a thought.