All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Alex Elsayed <eternaleye@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Kernel BUG on mounting BtrFS / after reboot
Date: Thu, 18 Feb 2010 10:02:38 -0500	[thread overview]
Message-ID: <20100218150238.GL10559@think> (raw)
In-Reply-To: <loom.20100218T013258-629@post.gmane.org>

On Thu, Feb 18, 2010 at 12:35:18AM +0000, Alex Elsayed wrote:
> Chris Mason <chris.mason <at> oracle.com> writes:
> 
> > 
> > On Fri, Feb 12, 2010 at 09:04:39PM +0000, Alex Elsayed wrote:
> > > I'm getting a rather nasty BUG when I try to mount this filesystem, 
> > > _including_ when I specify -o ro. I'm unsure what caused it, but the problem 
> > > manifested after my computer hardlocked while reading my RSS feeds, complete 
> > > with flashing lights. After I rebooted it, the screen filled with panic 
> > > messages when the initramfs tried to mount it RO to pivot into. I am running 
> > > 2.6.33-rc6. The BUG message is as follows:
> > 
> > The good news is this looks like a bug that Yan Zheng fixed.  2.6.33-rc7
> > or later should mount without problems.  If you're having trouble
> > getting that image onto that box, I'll get a usb boot image up with it
> > running for you.
> > 
> > -chris
> 
> No such luck. -rc8 still BUGs. Trace below:

Ugh ok.  The first thing I'd like to do is give you a patch to
completely disable the tree log replay and give you the chance to backup
critical data.

Do you already have a backup of the critical things on this drive?  The
problem you're hitting is that tree-logging code is trying to replay an
fsync of a file, but it can't find the file to replay.  This could be a
small and localized corruption or it could be a larger problem.  We'll
have to fix things one at a time to figure it out.

The easiest way to move forward would be to save a complete copy of the
FS with dd, but that's probably not very easy given the size.

-chris

  reply	other threads:[~2010-02-18 15:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-12 21:04 Kernel BUG on mounting BtrFS / after reboot Alex Elsayed
2010-02-12 22:50 ` Mike Fedyk
2010-02-12 22:59   ` Alex Elsayed
2010-02-17  6:47     ` Alex Elsayed
2010-02-17 14:18 ` Chris Mason
2010-02-18  0:35   ` Alex Elsayed
2010-02-18 15:02     ` Chris Mason [this message]
2010-02-18 17:38       ` Alex Elsayed
2010-02-18 20:48         ` Chris Mason
2010-02-18 20:54           ` Alex Elsayed
2010-02-23  8:30             ` Alex Elsayed
2010-02-25  1:40               ` 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=20100218150238.GL10559@think \
    --to=chris.mason@oracle.com \
    --cc=eternaleye@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.