From: Chris Mason <chris.mason@fusionio.com>
To: Mitch Harder <mitch.harder@sabayonlinux.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs-cleaner Blocked on xfstests 068
Date: Mon, 10 Jun 2013 08:26:28 -0400 [thread overview]
Message-ID: <20130610122628.4088.57887@localhost.localdomain> (raw)
In-Reply-To: <CAKcLGm-+19LiOaMzQ5b6dCboB_wGJNM_R=TP1ORVcJOgmj8s8A@mail.gmail.com>
Quoting Mitch Harder (2013-06-10 00:03:31)
> I'm running into a problem with the btrfs-cleaner thread becoming
> blocked on xfstests 068.
>
> The test locks up indefinitely without completing (normally it
> finished in about 45 seconds on my test box).
>
> I've replicated the issue on 3.10.0_rc5 and the for-linus branch of 3.9.0.
>
> I ran a git bisect on the 3.9.0 for-linus branch, and tracked my issue
> to the following commit:
>
> commit 9d1a2a3ad59f7ae810bf04a5a05995bf2d79300c
> btrfs: clean snapshots one by one
>
> The 068 test uses the scratch drive, so I believe xfs-test is using
> the defaults for formatting the device, which is a physical partition
> on my SATA drive.
>
> My mount settings for xfstests is:
> export MOUNT_OPTIONS="-o compress-force=lzo,autodefrag"
>
> There are no errors shown in dmesg. Here is the result of Alt-SysRq-W
> to show the blocked states:
This is a known problem between freeze and mount -o compress.
btrfs-next has a fix from Miao, but I wanted to be very cautious with
moving around unmount related mutexes.
-chris
prev parent reply other threads:[~2013-06-10 12:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 4:03 btrfs-cleaner Blocked on xfstests 068 Mitch Harder
2013-06-10 12:26 ` Chris Mason [this message]
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=20130610122628.4088.57887@localhost.localdomain \
--to=chris.mason@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mitch.harder@sabayonlinux.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).