From: Chris Mason <chris.mason@oracle.com>
To: Erik Jensen <eriksjunk@rkjnsn.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: kernel BUG when removing missing drive (Take 2)
Date: Wed, 20 Oct 2010 21:03:02 -0400 [thread overview]
Message-ID: <20101021010302.GW3400@think> (raw)
In-Reply-To: <AANLkTimu9bpQSPfM1fBsJHnWH-BwysvfKTaN2=d5w2gx@mail.gmail.com>
On Wed, Oct 20, 2010 at 05:53:34PM -0700, Erik Jensen wrote:
> After some more investigation, I discovered that for some reason btrfs
> is trying to write to the missing drive (devid 5) in the course of
> removing it from the array. Since this drive is missing, it is
> naturally not writable, leading to the BUG.
>
> If any other tests would be helpful in tracking down this problem,
> please let me know.
Ok, I'll reproduce this tonight and get a patch out during the day
tomorrow. Please don't do anything drastic with the drives, we can
definitely pull the data out.
-chris
next prev parent reply other threads:[~2010-10-21 1:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 2:17 kernel BUG when removing missing drive (Take 2) Erik Jensen
2010-10-21 0:53 ` Erik Jensen
2010-10-21 1:03 ` Chris Mason [this message]
2010-10-28 20:57 ` Chris Mason
2010-10-29 18:55 ` Erik Jensen
2010-10-31 11:58 ` Chris Mason
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=20101021010302.GW3400@think \
--to=chris.mason@oracle.com \
--cc=eriksjunk@rkjnsn.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