From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: xfs@oss.sgi.com
Subject: 3.0.1: xfs hang
Date: Sat, 20 Aug 2011 15:38:21 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1108201536510.14176@p34.internal.lan> (raw)
Hi,
Forgot to remove 'delaylog' from my fstab on one of my machines, while rm
-rf a large directory with many files:
[ 2880.313073] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 2880.313147] rm D 0000000100255dc1 0 2270 2253 0x00000000
[ 2880.313198] ffff88012b4f9810 0000000000000086 ffff8800bd632010 0000000000004000
[ 2880.313276] ffff88012b4f9810 ffff8800bd633fd8 ffff8800bd633fd8 0000000000000001
[ 2880.313352] ffff88012b4bf790 ffff88012b4f9a78 0000000412eec110 00000008bd633a58
[ 2880.313428] Call Trace:
[ 2880.313467] [<ffffffff810ceeb0>] ? mempool_alloc+0x60/0x140
[ 2880.313513] [<ffffffff812d272e>] ? submit_bio+0x5e/0xe0
[ 2880.313557] [<ffffffff815ded05>] ? schedule_timeout+0x1f5/0x250
[ 2880.313603] [<ffffffff812ab174>] ? xfs_buf_rele+0x74/0x110
[ 2880.313645] [<ffffffff815dfbd1>] ? __down+0x61/0xa0
[ 2880.313688] [<ffffffff812abf73>] ? _xfs_buf_find+0x163/0x260
[ 2880.313733] [<ffffffff81092666>] ? down+0x46/0x50
[ 2880.313775] [<ffffffff812aa459>] ? xfs_buf_lock+0x59/0xc0
[ 2880.313817] [<ffffffff812abf73>] ? _xfs_buf_find+0x163/0x260
[ 2880.313861] [<ffffffff812ac0da>] ? xfs_buf_get+0x6a/0x1b0
[ 2880.313906] [<ffffffff812ac244>] ? xfs_buf_read+0x24/0x110
[ 2880.313951] [<ffffffff812a2366>] ? xfs_trans_read_buf+0x206/0x400
[ 2880.313999] [<ffffffff8127577f>] ? xfs_da_do_buf+0x2af/0x770
[ 2880.314057] [<ffffffff81117869>] ? dput+0x39/0x310
[ 2880.314100] [<ffffffff81275cb4>] ? xfs_da_read_buf+0x24/0x30
[ 2880.314145] [<ffffffff8127a5db>] ? xfs_dir2_block_getdents+0xab/0x220
[ 2880.314193] [<ffffffff8127a5db>] ? xfs_dir2_block_getdents+0xab/0x220
[ 2880.314240] [<ffffffff81113e50>] ? filldir64+0xe0/0xe0
[ 2880.314283] [<ffffffff81113e50>] ? filldir64+0xe0/0xe0
[ 2880.314324] [<ffffffff81113e50>] ? filldir64+0xe0/0xe0
[ 2880.314366] [<ffffffff81278eea>] ? xfs_readdir+0xca/0x130
[ 2880.314410] [<ffffffff81113e50>] ? filldir64+0xe0/0xe0
[ 2880.314452] [<ffffffff812acfa4>] ? xfs_file_readdir+0x34/0x50
[ 2880.314497] [<ffffffff811140c8>] ? vfs_readdir+0xb8/0xd0
[ 2880.314542] [<ffffffff81114244>] ? sys_getdents+0x84/0xe0
[ 2880.314586] [<ffffffff815e0cbb>] ? system_call_fastpath+0x16/0x1b
(will remove delaylog, (but FYI))
Justin.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2011-08-20 19:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-20 19:38 Justin Piszcz [this message]
2011-08-25 5:18 ` 3.0.1: xfs hang Christoph Hellwig
2011-08-25 7:01 ` Justin Piszcz
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=alpine.DEB.2.02.1108201536510.14176@p34.internal.lan \
--to=jpiszcz@lucidpixels.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