From: Dave Chinner <david@fromorbit.com>
To: Lachlan McIlroy <lachlan@sgi.com>,
Christoph Hellwig <hch@infradead.org>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: deadlock with latest xfs
Date: Sun, 26 Oct 2008 11:53:51 +1100 [thread overview]
Message-ID: <20081026005351.GK18495@disturbed> (raw)
In-Reply-To: <20081024064804.GQ25906@disturbed>
On Fri, Oct 24, 2008 at 05:48:04PM +1100, Dave Chinner wrote:
> OK, I just hung a single-threaded rm -rf after this completed:
>
> # fsstress -p 1024 -n 100 -d /mnt/xfs2/fsstress
>
> It has hung with this trace:
>
> # echo w > /proc/sysrq-trigger
....
> [42954211.590000] 794877f8: [<6002e40a>] update_curr+0x3a/0x50
> [42954211.590000] 79487818: [<60014f0d>] _switch_to+0x6d/0xe0
> [42954211.590000] 79487858: [<60324b21>] schedule+0x171/0x2c0
> [42954211.590000] 794878a8: [<60324e6d>] schedule_timeout+0xad/0xf0
> [42954211.590000] 794878c8: [<60326e98>] _spin_unlock_irqrestore+0x18/0x20
> [42954211.590000] 79487908: [<60195455>] xlog_grant_log_space+0x245/0x470
> [42954211.590000] 79487920: [<60030ba0>] default_wake_function+0x0/0x10
> [42954211.590000] 79487978: [<601957a2>] xfs_log_reserve+0x122/0x140
> [42954211.590000] 794879c8: [<601a36e7>] xfs_trans_reserve+0x147/0x2e0
> [42954211.590000] 794879f8: [<60087374>] kmem_cache_alloc+0x84/0x100
> [42954211.590000] 79487a38: [<601ab01f>] xfs_inactive_symlink_rmt+0x9f/0x450
> [42954211.590000] 79487a88: [<601ada94>] kmem_zone_zalloc+0x34/0x50
> [42954211.590000] 79487aa8: [<601a3a6d>] _xfs_trans_alloc+0x2d/0x70
....
I came back to the system, and found that the hang had gone away - the
rm -rf had finished sometime in the ~36 hours between triggering the
problem and coming back to look at the corpse....
So nothing to report yet.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2008-10-26 0:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 9:17 deadlock with latest xfs Lachlan McIlroy
2008-10-23 20:57 ` Christoph Hellwig
2008-10-23 22:28 ` Dave Chinner
2008-10-24 3:08 ` Lachlan McIlroy
2008-10-24 5:24 ` Dave Chinner
2008-10-24 6:48 ` Dave Chinner
2008-10-26 0:53 ` Dave Chinner [this message]
2008-10-26 2:50 ` Dave Chinner
2008-10-26 4:20 ` Dave Chinner
2008-10-27 1:42 ` Lachlan McIlroy
2008-10-27 5:30 ` Dave Chinner
2008-10-27 6:29 ` Lachlan McIlroy
2008-10-27 6:54 ` Dave Chinner
2008-10-27 7:31 ` Lachlan McIlroy
[not found] ` <200810281702.17135.nickpiggin@yahoo.com.au>
2008-10-28 6:25 ` Dave Chinner
2008-10-24 8:46 ` Lachlan McIlroy
2008-10-26 22:39 ` Dave Chinner
2008-10-27 2:30 ` Timothy Shimmin
2008-10-27 5:47 ` Dave Chinner
2008-10-27 7:33 ` Lachlan McIlroy
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=20081026005351.GK18495@disturbed \
--to=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=lachlan@sgi.com \
--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