From: Alexander Beregalov <a.beregalov@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kernel Testers List <kernel-testers@vger.kernel.org>,
xfs@oss.sgi.com
Subject: 2.6.30-rc4: xfs_fsr hangs
Date: Sat, 2 May 2009 00:33:30 +0400 [thread overview]
Message-ID: <a4423d670905011333s664115bdh1d72392897567c1d@mail.gmail.com> (raw)
# xfs_db -r /dev/sdc1
xfs_db> frag
actual 23805, ideal 22890, fragmentation factor 3.84%
# xfs_fsr -v /dev/sdc1
/mnt/c start inode=0
ino=158
extents before:3 after:1 DONE ino=158
then it hangs
INFO: task xfs_fsr:2403 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
xfs_fsr D 00000000 4492 2403 1928
f3cc9dec 00000046 00000001 00000000 f3cc9de8 ec976680 ec976900 f2d06a50
ec976680 00000001 f2d06a50 f2d06a4c ffffffff f2d06a4c ec976680 f3cc9df4
c0447892 f3cc9e20 c04498ad f3cc9e28 f2d06a50 f2d06a74 f3cc9e44 00000246
Call Trace:
[<c0447892>] schedule+0x12/0x30
[<c04498ad>] rwsem_down_failed_common+0x6d/0x180
[<c04499dd>] rwsem_down_write_failed+0x1d/0x30
[<c0449a2a>] call_rwsem_down_write_failed+0x6/0x8
[<c026bfce>] ? xfs_ilock+0xee/0x100
[<c013fcd6>] ? down_write_nested+0x76/0x90
[<c026bfce>] ? xfs_ilock+0xee/0x100
[<c026bfce>] xfs_ilock+0xee/0x100
[<c0290fb4>] xfs_inactive+0x334/0x540
[<c01b382b>] ? inotify_inode_is_dead+0x1b/0x80
[<c029d4ef>] xfs_fs_clear_inode+0x1f/0x30
[<c019b7bb>] clear_inode+0x8b/0x110
[<c019bf06>] generic_delete_inode+0xe6/0x120
[<c0449d86>] ? _spin_lock+0x66/0x70
[<c019c09f>] generic_drop_inode+0x15f/0x230
[<c02c0958>] ? _atomic_dec_and_lock+0x18/0x40
[<c019b477>] iput+0x47/0x50
[<c0198a4f>] dentry_iput+0x6f/0xc0
[<c0198b74>] d_kill+0x24/0x50
[<c019a03b>] dput+0x5b/0x120
[<c018a892>] __fput+0x162/0x240
[<c018a98f>] fput+0x1f/0x30
[<c01873f7>] filp_close+0x47/0x70
[<c018748c>] sys_close+0x6c/0xd0
[<c0102e48>] sysenter_do_call+0x12/0x36
INFO: lockdep is turned off.
next reply other threads:[~2009-05-01 20:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-01 20:33 Alexander Beregalov [this message]
2009-05-02 10:14 ` Heinz Diehl
2009-05-02 18:35 ` Alexander Beregalov
2009-05-02 18:56 ` Eric Sandeen
2009-05-02 18:59 ` Alexander Beregalov
2009-05-02 20:14 ` Eric Sandeen
2009-05-03 1:47 ` Ed Tomlinson
2009-05-07 23:33 ` Eric Sandeen
2009-05-07 23:55 ` Eric Sandeen
2009-05-08 1:04 ` Felix Blyakher
2009-05-08 1:09 ` Eric Sandeen
2009-05-08 1:17 ` Felix Blyakher
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=a4423d670905011333s664115bdh1d72392897567c1d@mail.gmail.com \
--to=a.beregalov@gmail.com \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®