From: Liu Bo <bo.li.liu@oracle.com>
To: Torbjørn <lists@skagestad.org>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS hang with 3.16-rc5 (and also with 3.16-rc4)
Date: Wed, 30 Jul 2014 13:09:48 +0800 [thread overview]
Message-ID: <20140730050947.GB22510@localhost.localdomain> (raw)
In-Reply-To: <53D7B8B3.8000701@skagestad.org>
On Tue, Jul 29, 2014 at 05:07:31PM +0200, Torbjørn wrote:
> On 07/29/2014 12:18 PM, Liu Bo wrote:
> >On Mon, Jul 28, 2014 at 01:11:19PM +0200, Torbjørn wrote:
> >>On 28. juli 2014 12:00, Liu Bo wrote:
> >><snip>
> >>>This seems to be incomplete(Looks like dmesg has reached its buffer size limit),
> >>>does /var/log/message have the whole stack info?
> >>>
> >>>thanks,
> >>>-liubo
> >>Hi,
> >>
> >>Complete log was over 40MB. I uploaded everything from boot until
> >>"blocked for 120 seconds" started to appear.
> >>If you want all the trailing log as well, let me know.
> >>
> >>https://gist.github.com/anonymous/7958d8917967f727f324
> >Sorry...still don't get why it's locked up, io_ctl_prepare_pages() has several
> >callers, and they are properly released from the code level. And the warnings
> >printed in the log belong to other btrfs partitions, not the hanged btrfs one,
> >and we're still not able to know which one holds the free space cache inode page.
> >
> >Maybe we'd better resort to a bisect between 3.14 and 3.15(I know it'd be a lot
> >of time though).
> >
> >Here, doing rsync on compress=lzo full btrfs never hit that problem, shrug...
> >
> >thanks,
> >-liubo
> >
> >>--
> >>Torbjørn
> That's too bad.
>
> My reproducer is not 100% guaranteed to trigger the hang, so doing a
> bisect might lead us to some innocent commit.
> I have run the rsync + snapshot job several times here now, and no hang.
Good news! I've reproduced it with my xfstests config, will dig into it closer.
thanks,
-liubo
next prev parent reply other threads:[~2014-07-30 5:10 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 15:04 BTRFS hang with 3.16-rc5 Martin Steigerwald
2014-07-14 15:10 ` Martin Steigerwald
2014-07-14 17:51 ` Duncan
2014-07-14 22:03 ` Martin Steigerwald
2014-07-15 2:45 ` Duncan
2014-07-14 20:12 ` Chris Mason
2014-07-14 21:58 ` Martin Steigerwald
2014-07-15 13:21 ` Chris Mason
2014-07-15 15:08 ` Martin Steigerwald
2014-07-23 22:47 ` BTRFS hang with 3.16-rc5 (and also with 3.16-rc4) Martin Steigerwald
2014-07-24 14:58 ` Chris Mason
2014-07-24 16:24 ` Martin Steigerwald
2014-07-24 18:49 ` Martin Steigerwald
2014-07-24 20:04 ` Chris Mason
2014-07-28 22:57 ` Martin Steigerwald
2014-07-25 2:32 ` Duncan
2014-07-25 3:06 ` Nick Krause
[not found] ` <20140725080244.GA31950@carfax.org.uk>
2014-07-25 9:13 ` Hugo Mills
2014-07-28 13:20 ` David Sterba
2014-07-25 10:07 ` Martin Steigerwald
2014-07-25 4:51 ` Torbjørn
[not found] ` <20140725092800.GC25859@localhost.localdomain>
2014-07-25 10:22 ` Torbjørn
[not found] ` <53D23AF1.9010704@skagestad.org>
2014-07-25 11:37 ` Torbjørn
2014-07-25 16:14 ` Torbjørn
2014-07-28 10:00 ` Liu Bo
2014-07-28 11:11 ` Torbjørn
2014-07-29 10:18 ` Liu Bo
2014-07-29 15:07 ` Torbjørn
2014-07-30 5:09 ` Liu Bo [this message]
2014-07-18 7:51 ` BTRFS hang with 3.16-rc5 Martin Steigerwald
2014-07-18 13:36 ` Chris Mason
2014-07-19 17:59 ` Martin Steigerwald
2014-07-19 18:39 ` Chris Mason
2014-07-19 19:00 ` Martin Steigerwald
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=20140730050947.GB22510@localhost.localdomain \
--to=bo.li.liu@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@skagestad.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).