On 3 January 2017 at 19:58, L A Walsh <suse@tlinx.org> wrote:
Not entirely. If free space < 25%, it should stop keeping snapshots -- OR, it should allocate some fixed percentage of overall disk space when it is initialized -- like MS's ability to tune the amount of space for snapshots -- defaulting to ~10% or so.
If you have it dynamically using 50% of the free space, how will it respond if a user goes from 25% usage to 75% usage on their disk in one day (they created a several VM's maybe). If the space used by the snaps is contig, then not so much of a problem, but if it constantly shrinks and extends leaving fragments in the remaining free space, it will eventually hurt performance on large writes as well as overall read speed as free space becomes more and more fragmented over time.
I thought the default was 50% of the total space (excluding unusable space) on the root partition? That's what I read the Leap documentation on Snapper[1] as saying, as well as the documentation for the SPACE_LIMIT variable[2]. [1]: https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.ref... [2]: http://snapper.io/manpages/snapper-configs.html - Karl Cheng (Qantas94Heavy) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org