public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Elsayed <eternaleye@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Kernel BUG on mounting BtrFS / after reboot
Date: Wed, 17 Feb 2010 06:47:28 +0000 (UTC)	[thread overview]
Message-ID: <loom.20100217T074453-978@post.gmane.org> (raw)
In-Reply-To: loom.20100212T235536-583@post.gmane.org

Alex Elsayed <eternaleye <at> gmail.com> writes:

> 
> Mike Fedyk <mfedyk <at> mikefedyk.com> writes:
> 
> > 
> > On Fri, Feb 12, 2010 at 1:04 PM, Alex Elsayed <eternaleye <at> gmail.com> 
> 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:
> > 
> > Is this the bug you mentioned on IRC that you fixed somehow?
> > 
> > If so please post the steps you performed.
> 
> No, that bug was on a different hard drive and was due to bad blocks. That 
> instance was converted from ext4, while this is a new mkfs. The steps 
necessary 
> to reproduce the BUG are simple - mount -o ro /dev/Arkadios/Root $mountpoint.
> I'm currently running from my initramfs, with that old system  mounted ro and 
> bound to /usr (since that problem only occurred when writing to the disk, it 
> makes a passable recovery environment).

I have run btrfs-image on the partition, but due to it spanning the better part 
of 500GB (80% full), it's 1.1GB. I therefore can't attach it, but if there's 
somewhere I can FTP or otherwise upload it to so it can be examined, please let 
me know.


  reply	other threads:[~2010-02-17  6:47 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 [this message]
2010-02-17 14:18 ` Chris Mason
2010-02-18  0:35   ` Alex Elsayed
2010-02-18 15:02     ` Chris Mason
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=loom.20100217T074453-978@post.gmane.org \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox