From: Liu Bo <bo.li.liu@oracle.com>
To: Franke <ttfranke@googlemail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Crashes in extent_io.c after "btrfs bad mapping eb" notice
Date: Thu, 01 Nov 2012 10:39:32 +0800 [thread overview]
Message-ID: <5091E0E4.5080804@oracle.com> (raw)
In-Reply-To: <20121031210032.303c1c36@googlemail.com>
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>
thanks,
liubo
> I will probably destroy my btrfs and create a new one over the weekend,
> unless you still need info for debugging.
>
> thanks,
> Tobias
>
> On Wed, 31 Oct 2012 08:47:16 +0800
> Liu Bo <bo.li.liu@oracle.com> wrote:
>
>> On 10/31/2012 07:57 AM, Franke wrote:
>>> Hello,
>>>
>>> I have been having some crashes like this. Since I upgraded to
>>> 3.6.4 they have become common. The crashes happen pretty randomly
>>> during normal system usage. After the syslog messages the system
>>> stays semi usable for a minute, but when I run any new program it
>>> hangs. I had to downgrade to 3.6.2 to get my system usable again.
>>>
>>> Is there any way I can help find the cause of those crashes?
>>>
>>
>> Hi Franke,
>>
>> Jan and me have worked together to fix the mentioned bugs days
>> before, and you can try Jan's git repo and see if it works in your
>> situation:
>>
>> git.jan-o-sch.net for-chris
>>
>> (It contains most of patches related to backref walking.)
>>
>> thanks,
>> liubo
>>
next prev parent reply other threads:[~2012-11-01 2:39 UTC|newest]
Thread overview: 10+ 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 [this message]
2012-11-01 11:57 ` Jan Schmidt
2012-11-01 16:01 ` Jan Schmidt
2012-11-01 18:13 ` Tobias Franke
2012-10-31 3:46 ` Chris Samuel
-- strict thread matches above, loose matches on Subject: below --
2012-10-30 22:56 Franke
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=5091E0E4.5080804@oracle.com \
--to=bo.li.liu@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=ttfranke@googlemail.com \
/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.