On 26/02/17 12:07, Carlos E. R. wrote:
On 2017-02-26 09:02, Dr.-Ing. Dieter Jurzitza wrote:
Hello nicholas, have you ever tried to fix a broken Brtfs? I do not think so because your email tells me so.
The errors vary, btrfsck is simply not working, you are stuck every other time with a file system that is said to be full though it isnt. And there is no way to fix, try to find some information how to fix broken Btrfs file systems, you'll almost always fail. What partition size were you using?
I recommend a minimum size of 100 GiB for "/", with /home separate.
I let SuSE do its own thing, but what I picked up very early in investigating btrfs was a) the concept of "how much free space is there" doesn't make sense in a btrfs scenario. b) you do NOT want a "disk full" scenario - if you combine that with snapshots (which SuSE does as a matter of course for the root partition) you are just begging for a disaster to happen ...
If a root fs is broken, whom will you ask to fix anything if the tools available are simply disfunctional? Well, ask here. :-)
But you are right, the tools should work, automatically, and never make things worse.
c) btrfsck just shouldn't exist - it's been a disaster pretty much from day 1. Probably written for those people who demanded a fsck tool, by someone who didn't understand that btrfs was a work in progress and you can't run a bit-rotted fsck on an updated filesystem :-( aiui, btrfs as implemented in SuSE is a cut-down version, with most of the experimental and unstable features removed. The only known real problem is that one with snapshots and a disk full. Which a sys-admin should pick up and deal with before it becomes serious. Cheers, Wol -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org