On 26 February 2017 at 09:02, Dr.-Ing. Dieter Jurzitza <dieter.jurzitza@t-online.de> wrote:
Hello nicholas, have you ever tried to fix a broken Brtfs? I do not think so because your email tells me so.
I have, many times
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.
Well that is your problem, if the first thing you do with btrfs is run btrfsck, YOU are liable to break your btrfs filesystem This, and the correct procedure is well documented https://btrfs.wiki.kernel.org/index.php/Btrfsck The above URL is the first hit when I search for "btrfs repair" on duckduckgo, google and big
If a root fs is broken, whom will you ask to fix anything if the tools available are simply disfunctional?
How can we be sure the root fs is broken when you have no provided any of the requested information, and the only information you have provided demonstrates that you clearly didn't look after your root filesystem properly?
Search for "ext4 problem" and search for "btrfs problem". The differences are striking in numbers. There is even a wikipedia article listing tons of problems and may-be-circumvents for btrfs - I do not find anything similar for ext4. Guess why. ext4 problems are usually hardware problems - or someone ran into the overfull - limits. ext4 is simply more forgiving than Btrfs.
Guess what, I've lost more data in the last 5 years to ext4 than I have btrfs.. heck, even my home router is now running btrfs as it's root filesystem and I'm very comfortable with it -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org