Comment 3 for bug 1895943

Alright, I've read through some of these design docs. it's unfortunate they're buried in blog posts and not just laid out on an ubuntu site about zsys and zfs usage on Ubuntu, but at least now I know where they are.

More to the point, all I've done is watch some movies and download some games on steam, and within a month my system had unusably low disk space. So I'd definitely dispute your claim that my use case is "extreme". my use case is standard desktop usage, and not accounting for very normal usage in your design before shipping it with the OS is honestly unbelievable. if I was running server workloads with highly changing datasets, this would be way worse. I typically see > 1TB / week of writes on low usage servers, let alone the sometimes multiple TBs/hour on high usage systems, so I honestly can't imagine who this system design is for.

I'll try playing with a manually installed zsys.conf file and see if I can get this down to something usable. maybe if I just keep it to 2 old states instead of 20, that'd be more viable. I'd definitely recommend that the zsys.conf usage be documented in the package, either with a man page or a README under /usr/share/doc, since these implementation details seem pretty well hidden.