From: David Marcin <djmarcin@gmail.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Chris Mason <chris.mason@oracle.com>, linux-btrfs@vger.kernel.org
Subject: Re: BUG during btrfs device delete missing
Date: Mon, 12 Dec 2011 13:39:37 -0800 [thread overview]
Message-ID: <CAHh_JMOyrC76pe1ZyeZJWgY+51LVq57KDD6vPO32L1JQx5r-sQ@mail.gmail.com> (raw)
In-Reply-To: <4EE421EA.60809@cn.fujitsu.com>
On Sat, Dec 10, 2011 at 7:22 PM, Li Zefan <lizf@cn.fujitsu.com> wrote:
>>>> On Thu, Dec 08, 2011 at 11:06:47AM -0800, David Marcin wrote:
>>>>> raid10 metadata and data filesystem. =A0dmesg log follows. =A0The=
system
>>>>> is unable to unmount the filesystem after this occurs.
>>>>>
>>>>> Filesystem mounted at/mnt/btrfs with -o compress,degraded
>>>>> Command: btrfs device delete missing /mnt/btrfs
>>>>>
>>>>> [ =A0283.398222] ------------[ cut here ]------------
>>>>> [ =A0283.398289] kernel BUG at /home/apw/COD/linux/fs/btrfs/trans=
action.c:1329!
>>
>> So this crash means we failed to write all the blocks required to co=
mmit
>> the transaction. =A0The reason is that we're getting failed bios to =
the
>> missing device, and that failure isn't properly eaten by the
>> raid aware endio code.
>>
>> If you pull the top commit from my for-linus branch, it should all w=
ork.
>>
>> I know you've got a big FS here, I haven't tested this on raid10 yet=
,
>> only raid1. =A0If you want to wait a bit for safety I'll do a raid10=
run
>> too.
>>
>
> The fix looks good to me, and I've tested it on raid10.
Thanks Chris and Li. I can confirm that this fixed my issues on raid10=
as well.
David
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-12-12 21:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHh_JMPvmRNRrhh0aQhQiej+NP4Vb36MbFtECFphc8cUM9B=ZQ@mail.gmail.com>
2011-12-08 19:06 ` BUG during btrfs device delete missing David Marcin
2011-12-08 19:45 ` Chris Mason
2011-12-08 20:27 ` David Marcin
2011-12-09 16:52 ` Chris Mason
2011-12-11 3:22 ` Li Zefan
2011-12-12 21:39 ` David Marcin [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=CAHh_JMOyrC76pe1ZyeZJWgY+51LVq57KDD6vPO32L1JQx5r-sQ@mail.gmail.com \
--to=djmarcin@gmail.com \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lizf@cn.fujitsu.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).