From: Philip Seeger <p0h0i0l0i0p@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Crash during mount -o degraded, kernel BUG at fs/btrfs/extent_io.c:2044
Date: Sun, 1 Nov 2015 14:58:17 +0100 [thread overview]
Message-ID: <56361A79.7000301@googlemail.com> (raw)
In-Reply-To: <pan$a7ff8$b9ccf1a9$e2bf7f07$68b37eec@cox.net>
On 11/01/2015 04:22 AM, Duncan wrote:
> So what btrfs is logging to dmesg on mount here, are the historical error
> counts, in this case expected as they were deliberate during your test,
> nearly 200K of them, not one or more new errors.
>
> To have btrfs report these at the CLI, use btrfs device stats. To zero
Thanks for clarifying. I forgot to check btrfs dev stats. That explains it.
The 2-drive failure scenario still caused data corruption with 4.3-rc7
though.
Philip
next prev parent reply other threads:[~2015-11-01 13:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 23:13 Crash during mount -o degraded, kernel BUG at fs/btrfs/extent_io.c:2044 Erik Berg
2015-10-31 19:18 ` Philip Seeger
2015-10-31 23:36 ` Philip Seeger
2015-11-01 3:22 ` Duncan
2015-11-01 13:58 ` Philip Seeger [this message]
2015-11-01 13:44 ` Anand Jain
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=56361A79.7000301@googlemail.com \
--to=p0h0i0l0i0p@gmail.com \
--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).