All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: David Marcin <djmarcin@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: BUG during btrfs device delete missing
Date: Fri, 9 Dec 2011 11:52:06 -0500	[thread overview]
Message-ID: <20111209165206.GE8971@shiny> (raw)
In-Reply-To: <CAHh_JMOfLyHV=BSnW8J=8tn6huH0A2AvKqk6+WdOLCdG6zqkAA@mail.gmail.com>

On Thu, Dec 08, 2011 at 12:27:52PM -0800, David Marcin wrote:
> Hi Chris,
> This was on 3.2-rc2 but I tried with rc4 and it segfaulted again. =A0=
I
> think the traces were the same but I've rebooted and can't say for
> sure.
> David
> On Thu, Dec 8, 2011 at 11:45 AM, Chris Mason <chris.mason@oracle.com>=
 wrote:
> > Which kernel is this? =A0This looks like one I recently fixed.
> >
> > -chris
> >
> > 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/transa=
ction.c:1329!

So this crash means we failed to write all the blocks required to commi=
t
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=
=2E

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.

-chris
--
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

  reply	other threads:[~2011-12-09 16:52 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 [this message]
2011-12-11  3:22         ` Li Zefan
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=20111209165206.GE8971@shiny \
    --to=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.