3 ms·

> One thing to be aware of is it asked for the amount of space to leave free not how much to use, and got the size of my disk wrong by about a factor of 10 so I

> One thing to be aware of is it asked for the amount of space to leave free not how much to use, and got the size of my disk wrong by about a factor of 10 so I had to be a bit cautious about what I selected. Well, that's a deal-breaker for me. I can easily dedicate, say, a terabyte or two to the project, but I can't do "Free space minus this number". I need predictability.

sp332 11y ago
Isn't it more predictable to know that you'll have at least (say) 500MB free, instead of gradually filling up your drive until one day you don't have any more space? Edit: to be clear, it will actually remove backup data from the drive over time to maintain the amount of free space you set. It updates the central server to tell it which files you still have.
- Filligree 11y ago
  I have a 24TB disk array, configured as RAIDZ2; 12TB of usable space. When I run out of space, I add more disks. (Or, more usually, replace old ones.) I use Prometheus to keep track of its state, and have an email alert set up when disk space drops below a certain point. The problem with a program that tries to maintain a certain amount of free space is that I won't know how much space there really is. I'd need to subtract the amount the archive uses, then.. add back in the amount I actually want it to use.. and it all ends up as a bit of a mess. It'd be much easier for me if I could just set it to use 2TB, and be done with it. I could probably rely on it actually using the space.
  - sp332 11y ago
    I don't know if git-annex does that. Could you make a subvolume of the right size? Or create a new user and set its disk quota to the size you want?
IanCal 11y ago
Perhaps I worded that poorly, it's asking for the amount of space to not use. As in, on a 3TB drive, leave me 2TB for my own purposes and it'll then use a max of 1TB. It's not based on how utilised the drive currently is. My problem was it thought the drive was 16TB when in reality it was 2TB. That's a minor usability problem though, one I've been meaning to go and submit a PR for. Edit - As I understand it anyway.
- joeyh 11y ago
  I'd be interested in that bug report!

sp332 11y ago

Isn't it more predictable to know that you'll have at least (say) 500MB free, instead of gradually filling up your drive until one day you don't have any more space? Edit: to be clear, it will actually remove backup data from the drive over time to maintain the amount of free space you set. It updates the central server to tell it which files you still have.

Filligree 11y ago
I have a 24TB disk array, configured as RAIDZ2; 12TB of usable space. When I run out of space, I add more disks. (Or, more usually, replace old ones.) I use Prometheus to keep track of its state, and have an email alert set up when disk space drops below a certain point. The problem with a program that tries to maintain a certain amount of free space is that I won't know how much space there really is. I'd need to subtract the amount the archive uses, then.. add back in the amount I actually want it to use.. and it all ends up as a bit of a mess. It'd be much easier for me if I could just set it to use 2TB, and be done with it. I could probably rely on it actually using the space.
- sp332 11y ago
  I don't know if git-annex does that. Could you make a subvolume of the right size? Or create a new user and set its disk quota to the size you want?

IanCal 11y ago

Perhaps I worded that poorly, it's asking for the amount of space to not use. As in, on a 3TB drive, leave me 2TB for my own purposes and it'll then use a max of 1TB. It's not based on how utilised the drive currently is. My problem was it thought the drive was 16TB when in reality it was 2TB. That's a minor usability problem though, one I've been meaning to go and submit a PR for. Edit - As I understand it anyway.

joeyh 11y ago
I'd be interested in that bug report!