On Tue, 2021-01-05 at 09:56 -0500, Neal Gompa wrote:
On Tue, Jan 5, 2021 at 9:41 AM Richard Brown <rbrown@suse.de> wrote:
On Mon, 2020-12-21 at 19:06 +0100, Dario Faggioli wrote:
So, are there reasons why it's really preferable to keep the /home subvolume as nocow and I'm missing them? Or shall we switch it to cow?
There's one, which is the main reason I did it in the first place
GNOME Boxes (IMHO the best virtualisation tool) or virt-manager User Sessions puts qcow2 VM images in /home
Exactly! That was what I had in mind when we had that discussion, and why I also though nocow for /home as a whole would be good.
However, as Neal says...
libvirt, since 6.7.0, automatically provisions storage pools on btrfs with nodatacow by default. This obviates the need to have /home as nodatacow by default.
... This is already covered :-) And, thinking more about it, it's probably the case that having advanced features (like compression, etc) for _everything_in_home_ would be worth the hassle of going to the place where Boxes stores disk images and do a `chattr`. But, really, we don't even need to do that.
And in KDE there's database-like tools like akondi (sp?) with its datastore in /home
I don't think Akonadi does anything special when initializing its datastore on Btrfs, though I personally haven't worried about it either...
Ok, this is something I personally have no experience or idea... I'd think that what I said above (i.e., one can go in the proper place and do +C, if having issues... And of course we can document that) applies here to, but I'm open to opinions and suggesions. About the rest, I agree with Richard, that applies to openSUSE as a whole, so let's discuss the two things separately. Thanks, Regards and Happy New Year! :-D -- Dario Faggioli, Ph.D http://about.me/dario.faggioli Virtualization Software Engineer SUSE Labs, SUSE https://www.suse.com/ ------------------------------------------------------------------- <<This happens because _I_ choose it to happen!>> (Raistlin Majere)