now that I realize we already have what I wanted all the time ... this "Wasted" data per each data disk - I want a tiny bit more: just let it go negative! I don't know how to handle the total and I don't care about it at all myself but having "the negative waste" value would be incredibly useful.
Especially that wastage varies with the individual size of the files added to the data disk AND with the total size of the data ignored by snapraid it would be good to know if "the wastage" is for example -1 GiB or -40 GiB or -200 GiB. If you have a very low value you might have trouble with snapraid if you dump a lot of small files on that particular disk, if you have a high value, no problem. Now all would show as "0" so you can't tell which of the data disk needs more care and which one would be a good place to dump some thousands of files without any worry except the normal disk space there.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm bumping this, as it is pretty straightforward - in status.c make wasted int64_t instead of uint and remove all the logic that makes it only positive or 0 (and of course adjust the printf accordingly).
This is a very useful number, it is better to have a value for how much "breathing space" you have on each disk instead of having just a simple "0".
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Andrea,
now that I realize we already have what I wanted all the time ... this "Wasted" data per each data disk - I want a tiny bit more: just let it go negative! I don't know how to handle the total and I don't care about it at all myself but having "the negative waste" value would be incredibly useful.
Especially that wastage varies with the individual size of the files added to the data disk AND with the total size of the data ignored by snapraid it would be good to know if "the wastage" is for example -1 GiB or -40 GiB or -200 GiB. If you have a very low value you might have trouble with snapraid if you dump a lot of small files on that particular disk, if you have a high value, no problem. Now all would show as "0" so you can't tell which of the data disk needs more care and which one would be a good place to dump some thousands of files without any worry except the normal disk space there.
I'm bumping this, as it is pretty straightforward - in status.c make wasted int64_t instead of uint and remove all the logic that makes it only positive or 0 (and of course adjust the printf accordingly).
This is a very useful number, it is better to have a value for how much "breathing space" you have on each disk instead of having just a simple "0".
Hi John,
This change is now in SnapRAID 8.0.
Ciao,
Andrea
Thank you very much, I just installed the beta from today and works as expected!