Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
When attempting to
All directories on device allow touching a new file
Precise steps to reproduce the behavior
See script above
Please provide as much of the following information as possible:
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.