New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No Space Left on device #540
Comments
Does that directory exist on a device with sufficient space? You have minfreespace set to 20GB. Two of your drives are below that. Is the dir on one of those? |
It exists on disk3 and disk4
|
I had not been seeing this issue, until after updating to 2.25.1 |
Yeah, both are below your threshold. As the notes for 2.25.0 mention the silent fallback of policies was changed. It didn't work as users expected. You're using the path preservation policy. Only the drives with those directories are considered. Then you put a size limit. So it returns no space. What behavior would you expect with those settings? If you want all drives considered lfs policy would be the right policy. |
I'm experiencing a little bit similar issue (No space left on device error). That is not possible because I am using empty disks. Maybe the problem has something to with arch? I have this issue in a VM and on my old pc both and they both run arch. @SSS475 seems to be also using arch. |
@Eetsi123 If you don't describe your literal setup there is no way for me to assess the situation. Each policy was made more strict as described in the notes and docs. There are a number of conditions which can cause a branch to be ignored. Only a single error can be returned so they are prioritized. Without knowing exactly your setup I can't tell you which drive triggered which filter. As I mentioned prior according to his setup and the drive capacities the policy appears to be working as described. Pick the drive with that path and at least |
If you don't care about which drive gets the file you should not use a path preserving policy as it is by it's nature requiring you to manually manage some of the tree across drives. If you want it to use drives with the path usually but not error when everything fails the tests (as it does now) I'd need to add a new feature to not do path preserving in some cases. |
I'm not sure what wasn't working as expected. It worked perfectly fine for me. |
It does indeed work as described in the readme. Just different than the how it previously operated. But, I will tune my settings and get it to a place that works for me. Thanks. |
General description
When attempting to
touch
in one directory of a mergerfs volume I getNo space left on device
while other directories work fine.Expected behavior
All directories on device allow touching a new file
Actual behavior
Precise steps to reproduce the behavior
See script above
System information
Please provide as much of the following information as possible:
mergerfs -V
cat /etc/fstab
or the command line argumentsOnly relevant lines
uname -a
None
df -h
df -h
df -i
strace -f -o /tmp/app.strace.txt <cmd>
orstrace -f -p <appPID> -o /tmp/app.strace.txt
strace -f -p <mergerfsPID> -o /tmp/mergerfs.strace.txt
The text was updated successfully, but these errors were encountered: