mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

annex.diskreserve default increased from 1 mb to 100 mb

Browse source 
It's hard to know what's a good default for this. But 1 mb seems way too
small, because it's very easy for a git pull or some similar operation
that we don't think of as using much space to use up 1 mb of space.

Most people would want to free up some space if a filesystem only had 100
mb free. But on a small VPS, it's probably not uncommon to have only 1 gb
free. So 1 gb is too large for annex.diskreserve.

While old 1 gb USB keys are around, it's unlikely that anyone is
relying on them to shuttle annex data around; it would be worth anyone's
time to upgrade to a 32 gb or larger cheap modern USB key ($5).

Sponsored-by: Kevin Mueller on Patreon
This commit is contained in:
Joey Hess 2022-09-21 15:00:13 -04:00
parent 94216c99a7
commit 34e313f786
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
4 changed files with 8 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

1
doc/todo/prevent_pulling_unlocked_files_using_all_disk_space_by_default.mdwn
View file

@ -9,6 +9,7 @@ be eaten up by other non-object uses of disk.
Perhaps 1 mb is too small for the default for annex.diskreserve. Even
10 or 100 mb would leave a lot more margin for other minor uses of disk space.
(Update: increased default to 100 mb)
Perhaps there could be another config like annex.diskreserve but that
applies only to populating unlocked files. It could default to some larger