On 05/04/2015 01:47 PM, Carlos E. R. wrote:
However, I have seen several people come with problems to the forums, with some breakage or other caused by having btrfs, and when asked, they didn't even know they were using it.
They just accepted the defaults. I would, in their place.
maybe its that I'm an engineer at heart or maybe its that I'm just plain curious, but I never 'just accept' anything. OK, so some things like credit cards I can't 'negotiate' terms, but I still read and try to comprehend the agreements. I know how all the devices I won work. I research most of the things I buy beforehand, read the labels on the products at the supermarket. Excessive? I don't think so, not in this day and age. I'm not an Eco-Nit or a anti-GMO protester, just .... Careful. I've found some food additives that I react badly to and avoid them. Sometimes the labels "Low Salt" and "fat Free" are .... Misleading. "Just accept" is what a lot of vendors expect you to do.
The most frequent problem is the root partition filling up,
That has always been the case. Its why I use LVM In the limiting case, if my hard drive fills up totally, LVM will let me extend onto another drive :-)
and the traditional advice to solve this doesn't work.
What 'traditional' advice are you talking about? Some methods work with all file systems: "make sure you have a backup, repartition & reload" is one. How does that 'not work'? You can grow the FS, just like ext4, ReiserFS, XFS, if you can grow the partition. Oh, right, back to LVM :-) And oh yes, I had a nearly full chogged BtrFS root, but rather than bitch and complain here about it, I did something. I grew the LVM partition and I grew the BtrFS. Added another 30G :-) Worked OK. Please not: I did something that was quite reasonable, something I've done with RootFS that have been ReiserFS and Ext4 in the past. And it worked. Wrote
The cause, IMO, is that the root filesystem when using btrfs should be at least 50 GB, and if that is not possible, YaST should default to ext4 instead.
That strikes me as sensible. Hmm looks like its possible to set up autoyast to do that.
On other occasions the filesystem corrupts, fsck doesn't work, and repair becomes very complicated. Few people know how to repair it (I don't).
Well that takes me back to the 1970s and 1980s. Few sysadmins knew how to repair a V6/V7 file system. FSCK could pick up some pieces and put them in the lost+found, just as some versions of fsck can today, but more likely than not any open files, anything since the last sync, was lost. BTDT, learnt a LOT about the V6/V7 FS and how badly it managed metadata. I made some mods to the scheduling algorithm that increased FS integrity but at the cost of performance, then was told to take them out. Isn't that always the case: speed trumps reliability and integrity every time. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org