[Hideki Yamane] >> Could snapper be changed to restrict the amount of snapshots kept in >> each category based on amount of free space on the file system, to avoid >> filling up the disk with snapshots? > > Unfortunately, no. However, you can limit snapshots by "numbers".
Any hope to have such feature implemented, as snapper in its current form is dangerous as long as btrfs start blocking processes when the disk is full. :( > One btrfs guy says it's hard to do such behavior since btrfs snapshots > share same blocks as those snapshot data, so not sure how to keep > amount of disk by deleting old snapshots. One way would be to not take snapshots if df show less than X % free space. Another would be to start removing old snapshots until df show more than X % free space before doing any snapshots. The point is that for me it is better to not take snapshots than to bring down the entire service. :) >> It would be great if snapper also provided a way to easily figure out >> how much disk space a given snapshot uses. > > Said above, most of snapshots share same blocks, it's hard I guess. A way to do this is documented in <URL: https://raw.githubusercontent.com/agronick/btrfs-size/master/btrfs-size.sh >. > Could you give me some examples, please? Sure, check out <URL: https://github.com/zfsnap/zfsnap/wiki/zfSnap >. -- Happy hacking Petter Reinholdtsen
