From: Li Zefan <lizf@cn.fujitsu.com>
To: Chris Mason <chris.mason@oracle.com>,
David Marcin <djmarcin@gmail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: BUG during btrfs device delete missing
Date: Sun, 11 Dec 2011 11:22:18 +0800 [thread overview]
Message-ID: <4EE421EA.60809@cn.fujitsu.com> (raw)
In-Reply-To: <20111209165206.GE8971@shiny>
>>> On Thu, Dec 08, 2011 at 11:06:47AM -0800, David Marcin wrote:
>>>> raid10 metadata and data filesystem. dmesg log follows. The 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
>>>>
>>>> [ 283.398222] ------------[ cut here ]------------
>>>> [ 283.398289] kernel BUG at /home/apw/COD/linux/fs/btrfs/transaction.c:1329!
>
> So this crash means we failed to write all the blocks required to commit
> the transaction. The 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 work.
>
> I know you've got a big FS here, I haven't tested this on raid10 yet,
> only raid1. If 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.
next prev parent reply other threads:[~2011-12-11 3:22 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 [this message]
2011-12-12 21:39 ` David Marcin
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=4EE421EA.60809@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=chris.mason@oracle.com \
--cc=djmarcin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.