From: Tobias Franke <ttfranke@googlemail.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Crashes in extent_io.c after "btrfs bad mapping eb" notice
Date: Thu, 1 Nov 2012 19:13:45 +0100 [thread overview]
Message-ID: <20121101191345.3a3adf26@googlemail.com> (raw)
In-Reply-To: <5092638C.2070505@jan-o-sch.net>
Hi,
I have been trying to get some sysrq output, but I am only getting hard
hangs right now. So no reaction to sysrq-w.
Here is some sysrq-w output from around 15 minutes before the crash:
https://www.dropbox.com/s/386ifyoxh8eppia/sysrqw_2012-11-1.log
I don't know if this will be helpful.
Tobias
On Thu, 01 Nov 2012 12:57:00 +0100
Jan Schmidt <list.btrfs@jan-o-sch.net> wrote:
> On Thu, November 01, 2012 at 03:39 (+0100), Liu Bo wrote:
> > On 11/01/2012 04:00 AM, Franke wrote:
> >> Hi,
> >>
> >> since yesterday I have run a balance while asleep/at work. Now I
> >> experimented a bit, and the situation has changed.
> >>
> >> I am now getting hard hangs ( system is gone without even writing
> >> anything to syslog ), some time ( minutes to an hour ) into
> >> running a scrub.
> >>
> >> Those hangs happen with 3.6.2 , 3.6.4 and Jan's unstable version.
> >> It hasn't hung yet without running a scrub.
> >>
> >> I have no idea if this is part of the same problem or something
> >> else. Do you have any idea either way?
> >>
> >
> > Well, thanks for testing.
> >
> > We may need your sysrq-w output(maybe screen output) to locate
> > where we hard hangs.
> >
> > Besides, I recommend you pick Jan's patches out, and apply them on
> > the latest btrfs upstream and run another round to see if it get
> > better, since there might be some fixes for the very hang already
> > in the upstream.
> >
> > Right now the latest btrfs upstream's top commit is
> >
> > commit f46dbe3dee853f8a860f889cb2b7ff4c624f2a7a
> > Author: Chris Mason <chris.mason@fusionio.com>
> > Date: Tue Oct 9 11:17:20 2012 -0400
> >
> > btrfs: init ref_index to zero in add_inode_ref
> >
> > Signed-off-by: Chris Mason <chris.mason@fusionio.com>
>
> This is an old top commit. The current cmason/master state is
>
> commit c37b2b6269ee4637fb7cdb5da0d1e47215d57ce2
> Author: Josef Bacik <jbacik@fusionio.com>
> Date: Mon Oct 22 15:51:44 2012 -0400
>
> and includes my recent fixes. I don't really expect them to prevent
> getting stuck anywhere. sysrq+w output would be really helpful. I'm
> trying to reproduce the problems in the meantime.
>
> -Jan
next prev parent reply other threads:[~2012-11-01 18:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 23:57 Crashes in extent_io.c after "btrfs bad mapping eb" notice Franke
2012-10-31 0:47 ` Liu Bo
2012-10-31 0:50 ` Liu Bo
2012-10-31 20:00 ` Franke
2012-11-01 2:39 ` Liu Bo
2012-11-01 11:57 ` Jan Schmidt
2012-11-01 16:01 ` Jan Schmidt
2012-11-01 18:13 ` Tobias Franke [this message]
2012-10-31 3:46 ` Chris Samuel
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=20121101191345.3a3adf26@googlemail.com \
--to=ttfranke@googlemail.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;
as well as URLs for NNTP newsgroup(s).