On Thu, Sep 15, 2016 at 11:05 AM, Ronan Arraes Jardim Chagas <ronisbr@gmail.com> wrote:
Hi Chris,
Em qui, 2016-09-15 às 10:37 -0600, Chris Murphy escreveu:
So basically, you're just going to have to wait until they have something to report and a fix. And/or reinstall and use XFS or something if you can't wait. *shrug* that is an explanation. It's not a great one for you, but that's where things are at.
Yes, that is precisely why I said that no good explanation was provided yet :)
As of now, I am not even sure how safe is the data in the BTRFS partition. Since I don't know what is happening and what is causing it, how can I be 100% sure that my data will be safe? Hence, all my sensible data was moved to EXT4. I mentioned a workaround in btrfs mailing list that I think can help me, so I will continuous to use BTRFS in root.
Seeing as you're in an edge case, the file system could implode at any time. Chances are it'd just go read only and you'd still be able to get your data off the volume, even if the file system is broken beyond repair.
Actually, I am only using BTRFS now just because I embrace FOSS and I am an openSUSE member. Hence, I see as my responsibility to help fixing it. Unfortunately, I do not have technical skills to dig the source code, but I can help sending these huge e-mails with all the debug data I can collect :)
I think your contribution has been helpful.
In the mean time, I think it is wise to verify how stable BTRFS is in Tumbleweed to avoid other users to hit the same problem, which can be very bad if you don't know what is happening or what to do to fix it. This is why I started this thread.
It's important to not extrapolate one's own experience. If I were to do the same thing based on my experience with Btrfs, I'd say make it the default everywhere, because I've had so few problems (that weren't deliberately self created for the purpose of testing). The truth is it depends on the use case and user preference. In the unlikely event the file system has a problem it can't fix at mount time, Btrfs fixing quickly becomes non-trivial, non-obvious, and not for a typical user. Even in the current version of btrfs-progs the fsck with --repair is listed as do not use except under advisement by a developer, and as being dangerous. And then there are a bunch of other repairs, zero-log, chunk-recover, super-recover, init-csum-tree, init-extent-tree, and so on. It's hard to know what to do and in what order, more difficult than any other file system on Linux. So it goes from easy to WTF very quickly. -- Chris Murphy -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org