From: Dave Chinner <david@fromorbit.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: xfs@oss.sgi.com
Subject: Re: XFS in a XFS locks up in xfs_ilock
Date: Sat, 24 Oct 2009 13:41:24 +1100 [thread overview]
Message-ID: <20091024024124.GF9464@discord.disaster> (raw)
In-Reply-To: <alpine.LSU.2.00.0910231957570.5688@obet.zrqbmnf.qr>
On Fri, Oct 23, 2009 at 08:02:08PM +0200, Jan Engelhardt wrote:
> Hi,
>
>
> it seems that somewhere, locking is afoul in XFS so that having a
> loopback XFS on an XFS causes a deadlock, first on the subvolume, then
> on the real one. Sometimes that happens within writing a few MB to the
> subvolume (the loop one), sometimes nothing happens and it can be used
> for many months.
>
> Suggested testcase:
>
> Starting out with $HOME being on xfs (truncate is coreutils 7+):
> $ >disk
> $ truncate --size=$[3*1048576*1024] disk
> So it's actually sparse(!)
> $ mkfs.xfs disk
> # mount disk mnt -oloop
>
> Start filling it with data, preferably something like installing a bunch
> of rpm/debs into mnt, and hopefully soon enough, the thing will lock up.
> xfs_ilock I got from `ps xaf -o wchan` while a box was shortly before
> dying - processes were stuck in D state. Not sure if this is related to
> the sparseness of the file, but I would bet it's part of the problem.
Can you provide the output of sysrq-w (echo w > /proc/sysrq-trigger)
so we can see stacks of the threads stuck in D state?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-10-24 2:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 18:02 XFS in a XFS locks up in xfs_ilock Jan Engelhardt
2009-10-24 2:41 ` Dave Chinner [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=20091024024124.GF9464@discord.disaster \
--to=david@fromorbit.com \
--cc=jengelh@medozas.de \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox