From: Josef Bacik <josef@redhat.com>
To: Chris Mason <chris.mason@oracle.com>,
Josef Bacik <josef@redhat.com>,
Francesco Cepparo <francesco.cepparo@gmail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: kernel BUG at fs/btrfs/extent_io.c:1890!
Date: Thu, 12 Apr 2012 14:20:49 -0400 [thread overview]
Message-ID: <20120412182049.GK1924@localhost.localdomain> (raw)
In-Reply-To: <20120412181525.GU29506@shiny>
On Thu, Apr 12, 2012 at 02:15:25PM -0400, Chris Mason wrote:
> On Thu, Apr 12, 2012 at 02:08:37PM -0400, Josef Bacik wrote:
> > On Wed, Apr 11, 2012 at 11:59:43PM +0000, Francesco Cepparo wrote:
> > > I tried your patch but unfortunately the kernel still gives me the
> > > same error message :(
> >
> > Weird, will you apply this patch on top of the one I sent you and send me the
> > dmesg when it panics again? Thanks,
> >
> > Josef
> >
> > diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
> > index 2a3ddd2..51efb58 100644
> > --- a/fs/btrfs/disk-io.c
> > +++ b/fs/btrfs/disk-io.c
> > @@ -652,6 +652,8 @@ static int btree_io_failed_hook(struct page *page, int failed_mirror)
> >
> > eb = (struct extent_buffer *)page->private;
> > set_bit(EXTENT_BUFFER_IOERR, &eb->bflags);
> > + WARN_ON(!failed_mirror);
> > + printk(KERN_ERR "io error, failed mirror %d\n");
> ^^^^^
>
> , failed_mirror
>
pfft compiling debug patches before sending them out is for losers,
Josef
next prev parent reply other threads:[~2012-04-12 18:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 14:44 kernel BUG at fs/btrfs/extent_io.c:1890! Francesco Cepparo
2012-04-11 15:01 ` Josef Bacik
2012-04-11 23:59 ` Francesco Cepparo
2012-04-12 18:08 ` Josef Bacik
2012-04-12 18:15 ` Chris Mason
2012-04-12 18:20 ` Josef Bacik [this message]
2012-04-12 21:56 ` Francesco Cepparo
2012-04-13 14:45 ` Josef Bacik
2012-04-14 0:06 ` Francesco Cepparo
2012-04-16 13:34 ` Josef Bacik
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=20120412182049.GK1924@localhost.localdomain \
--to=josef@redhat.com \
--cc=chris.mason@oracle.com \
--cc=francesco.cepparo@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.