From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS RAID5 filesystem corruption during balance
Date: Sat, 23 May 2015 02:56:06 +0000 (UTC) [thread overview]
Message-ID: <pan$2d29f$68e50c54$420ff0f1$97d19c19@cox.net> (raw)
In-Reply-To: CAJCQCtTeoYHganNAJf=cyXzgCN9z1X=G1N=xEbksyRVDpZPbjQ@mail.gmail.com
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@cox.net> 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
prev parent reply other threads:[~2015-05-23 2:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 21:43 BTRFS RAID5 filesystem corruption during balance Jan Voet
2015-05-22 4:43 ` Duncan
2015-05-22 18:11 ` Jan Voet
2015-05-23 15:02 ` Jan Voet
2015-06-20 3:50 ` Russell Coker
2015-05-22 19:15 ` Chris Murphy
2015-05-23 2:56 ` Duncan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='pan$2d29f$68e50c54$420ff0f1$97d19c19@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).