Chris Murphy posted on Fri, 22 May 2015 13:15:09 -0600 as excerpted: > On Thu, May 21, 2015 at 10:43 PM, Duncan <1i5t5.duncan@xxxxxxx> wrote: >> For in-production use, therefore, btrfs raid56 mode, while now at least >> in theory complete, is really too immature at this point to recommend. > > At some point perhaps a developer will have time to state the expected > stability level on stable hardware. And what things should be included > in a complete report. I see many reports only including the bug/ Warning > with call trace. And too often problems were happening before that. > > The XFS FAQ has an explicit "what to include in a report" other that may > serve as a guide to adapt for Btrfs reports. There's one spot on the wiki (bottom of the btrfs mailing lists page) that lists the information to provide when filing a bug. https://btrfs.wiki.kernel.org/index.php/Btrfs_mailing_list But, even being somewhat familiar with the wiki and knowing it was, or had been, somewhere on the wiki, I had trouble finding it. It's definitely not in the first place I looked, the Problem FAQ, under How do I report bugs and issues? (Tho it does link to the list page.) https://btrfs.wiki.kernel.org/index.php/Problem_FAQ#How_do_I_report_bugs_and_issues.3F If I had ever gotten around to getting a wiki login, I'd fix that, but for some reason, while I seem to be fine posting to newsgroups and mailinglists (as newsgroups, via gmane.org's list2news service), I mostly treat the web, wikis included, as read-only, other than the occasional reply to an article. I never got into web forums that much either. So if you have a wiki login and time to fix it... =:^) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
