From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Cc: Chandra Seetharaman <sekharan@us.ibm.com>
Subject: [regression 3.11-rc1] unmount hanging purging quotas
Date: Thu, 18 Jul 2013 21:09:31 +1000 [thread overview]
Message-ID: <20130718110931.GA13468@dastard> (raw)
Hi Chandra,
I'm seeing xfs/050 hanging on a current oss-xfs master tree during
unmount getting stuck purging dquots. it basically loops there
forever. Have you seen anything like this recently?
# echo w > /proc/sysrq-trigger
[ 5179.063824] SysRq : Show Blocked State
[ 5179.064895] task PC stack pid father
[ 5179.066459] umount D ffff88007fd13280 5592 27782 26800 0x00000000
[ 5179.067478] ffff88007b747b98 0000000000000046 ffff8800524e4500 ffff88007b747fd8
[ 5179.067478] ffff88007b747fd8 ffff88007b747fd8 ffff88007c83dc00 ffff8800524e4500
[ 5179.067478] ffff88007b747b88 ffff88007b747bd0 ffff88007c858000 0000000100129cb6
[ 5179.067478] Call Trace:
[ 5179.067478] [<ffffffff81c53319>] schedule+0x29/0x70
[ 5179.067478] [<ffffffff81c4fa3b>] schedule_timeout+0x10b/0x1f0
[ 5179.067478] [<ffffffff8109a1e0>] ? usleep_range+0x50/0x50
[ 5179.067478] [<ffffffff814d8c20>] ? xfs_qm_need_dqattach+0x80/0x80
[ 5179.067478] [<ffffffff81c4fb3e>] schedule_timeout_uninterruptible+0x1e/0x20
[ 5179.067478] [<ffffffff814d911b>] xfs_qm_dquot_walk+0x19b/0x1b0
[ 5179.067478] [<ffffffff81c54934>] ? _raw_spin_lock_irqsave+0x24/0x30
[ 5179.067478] [<ffffffff8174c3ad>] ? do_raw_spin_unlock+0x5d/0xb0
[ 5179.067478] [<ffffffff810a77e4>] ? flush_work+0x34/0x160
[ 5179.067478] [<ffffffff8109b354>] ? del_timer+0x54/0x70
[ 5179.067478] [<ffffffff810a9461>] ? try_to_grab_pending+0xd1/0x190
[ 5179.067478] [<ffffffff814d9170>] xfs_qm_dqpurge_all+0x40/0x90
[ 5179.067478] [<ffffffff814d9d65>] xfs_qm_unmount+0x25/0x40
[ 5179.067478] [<ffffffff8147065c>] xfs_unmountfs+0x7c/0x120
[ 5179.067478] [<ffffffff814735c5>] xfs_fs_put_super+0x25/0x60
[ 5179.067478] [<ffffffff81191aa1>] generic_shutdown_super+0x61/0xf0
[ 5179.067478] [<ffffffff81191b60>] kill_block_super+0x30/0x80
[ 5179.067478] [<ffffffff81191fdd>] deactivate_locked_super+0x4d/0x80
[ 5179.067478] [<ffffffff81192b8e>] deactivate_super+0x4e/0x70
[ 5179.067478] [<ffffffff811adaf1>] mntput_no_expire+0x101/0x160
[ 5179.067478] [<ffffffff811aec9c>] SyS_umount+0x9c/0x3a0
[ 5179.067478] [<ffffffff81c5d419>] system_call_fastpath+0x16/0x1b
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2013-07-18 11:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 11:09 Dave Chinner [this message]
2013-07-18 12:02 ` [regression 3.11-rc1] unmount hanging purging quotas Jeff Liu
2013-07-18 13:58 ` Chandra Seetharaman
2013-07-18 16:33 ` Chandra Seetharaman
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=20130718110931.GA13468@dastard \
--to=david@fromorbit.com \
--cc=sekharan@us.ibm.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 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.