From: Anand Jain <anand.jain@oracle.com>
To: Philip Seeger <p0h0i0l0i0p@gmail.com>,
Erik Berg <btrfs@slipsprogrammoer.no>,
linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.cz>
Subject: Re: Crash during mount -o degraded, kernel BUG at fs/btrfs/extent_io.c:2044
Date: Sun, 1 Nov 2015 21:44:54 +0800 [thread overview]
Message-ID: <56361756.4060705@oracle.com> (raw)
In-Reply-To: <5635140F.7040206@googlemail.com>
> This is misleading, these error messages might make one think that the
> 4th drive is bad and has to be replaced, which would reduce the
> redundancy to the minimum because it's the second drive that's actually
> bad.
following RFC will solve the misleading part of the problem..
[RFC PATCH] Btrfs: fix fs logging for multi device
Thanks, Anand
prev parent reply other threads:[~2015-11-01 13:45 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
2015-11-01 13:44 ` Anand Jain [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=56361756.4060705@oracle.com \
--to=anand.jain@oracle.com \
--cc=btrfs@slipsprogrammoer.no \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=p0h0i0l0i0p@gmail.com \
/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).