On 8/29/16 5:42 PM, Lindsay Mathieson wrote:
On 30/08/2016 1:56 AM, Ronan Arraes Jardim Chagas wrote:
I just have the problem again. Now, it happens during the lunch time when the machine was idle. Only the system processes were running. It was not the first time that I saw this problem just after lunch when the machine stayed idle for a long period (+- 1h). This time, only the reboot worked, I could not run balance.
Given the debacle over RAID 5/6 and the ongoing issues with stability, and supposedly a very messy codebase, is btrfs still a wise default for installs?
Those are three separate issues. The first is, from our (SUSE) perspective, isn't an issue. We don't support RAID 5/6, full stop. We don't support device replace either, since those features aren't ready for prime time. Those "not supported" rules would apply to openSUSE too, but when I asked about adding the "allow_unsupported" option to openSUSE years ago, we never reached a consensus. The third is irrelevant for anyone not working on the code. Could it use improvement? Sure, but that's an ongoing process. For the most part, we're cleaning up the messes that came with trying to grow the developer base when it was still a skunkworks project. Lesson for future projects: don't do that. Lastly, the stability issues. I mostly see bug reports fall into a few buckets. The "OMG my file system is gone now" bugs haven't been common for a long time. Qgroups bugs are still a problem for a variety of reasons, but we're getting close to squashing the last of them. People do run into ENOSPC occasionally, but nowhere near as often as they did years ago. I think the main thing is that the number of users of btrfs has gone up drastically but the bugs reported haven't. -Jeff -- Jeff Mahoney SUSE Labs