Hello, Am Freitag, 16. November 2018, 17:05:54 CET schrieb Richard Brown:
On Fri, 16 Nov 2018 at 16:58, Robert Munteanu wrote:
Have you considered disabling copy-on-write for the /home subvolume? It is (in my limited experience) the primary thing that can suprise users in a nasty way under /home.
The thought crossed my mind, but I don't think it makes sense here
Unlike /var, the chances of users having data which will benefit from NoCoW is relatively small - how many users have relational databases stored their /home?
That number might not be as smallas you think ;-) KMail / Akonadi uses a MySQL database, so nearly all KMail users have a database in their home directory (unless they change the Akonadi config to use the system-wide MySQL or PostgreSQL). The various desktop searches like Baloo also use something that looks like a database to me ;-)
My personal systems have been running for over a year using the config I'm now proposing for everyone by default, and there's no way in heck I could live with /home with CoW disabled.
Just curious - how big is your btrfs partition? I have a ~500 GB btrfs since some months, and had a few cases where one of the btrfs-* (IIRC balance) cronjobs (actually timers) made the system mostly unusable for some minutes by causing a high IO load. Is this a known issue, or should I report a bug if/when it happens again? (I'm aware of boo#1063638, but I'm not sure if it matches my problem, and given the number of comments I slightly ;-) doubt if adding even more comments there is a good idea ;-) Regards, Christian Boltz -- Registrierter Linux-Nutzer #239431 Linux is like a wigwam: no gates, no windows, but an apache inside. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org