From: Jim <jim@webstarts.com>
To: linux-btrfs@vger.kernel.org
Subject: ls hangs filesystem
Date: Tue, 18 Oct 2011 09:25:46 -0400 [thread overview]
Message-ID: <4E9D7E5A.2010403@webstarts.com> (raw)
Good morning btrfs list,
I have been rsyncing files from an nfs mount to a btrfs filesystem.
After an rsync run I ls random subvols or directorys to check the copy.
About 60% to 70% of the time ls completely hangs. Ps aux shows it as
running but even when I let it go for up to an hour it never finishes.
Kill -9 will not stop the process. Dmesg shows nothing beyond a
successful mount at boot. I can't umount the system because "filesystem
is busy". I find that a forced reboot is the only way to recapture the
system. /var/log/messages has the only indication (that I can find)
that anything abnormal is happening. A tail of the file is below.
Thank you for any help and advice.
Jim
[root@btrfs ~]# tail -20 /var/log/messages
Oct 18 05:06:36 btrfs kernel: [<ffffffff81142849>] sys_getdents+0x89/0xf0
Oct 18 05:06:36 btrfs kernel: [<ffffffff814b19ab>]
system_call_fastpath+0x16/0x1b
Oct 18 05:08:36 btrfs kernel: INFO: task ls:7100 blocked for more than
120 seconds.
Oct 18 05:08:36 btrfs kernel: "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Oct 18 05:08:36 btrfs kernel: ls D ffff88080bc843d8 0
7100 7047 0x00000084
Oct 18 05:08:36 btrfs kernel: ffff8804f526dd68 0000000000000086
ffff8804f526dd18 ffffffff00000000
Oct 18 05:08:36 btrfs kernel: ffff88080bc84000 0000000000011900
ffff8804f526dfd8 ffff8804f526c010
Oct 18 05:08:36 btrfs kernel: ffff8804f526dfd8 0000000000011900
ffff88080f64d7f0 ffff88080bc84000
Oct 18 05:08:36 btrfs kernel: Call Trace:
Oct 18 05:08:36 btrfs kernel: [<ffffffffa01a0f45>]
wait_current_trans+0xa5/0x110 [btrfs]
Oct 18 05:08:36 btrfs kernel: [<ffffffff8106c0e0>] ? wake_up_bit+0x40/0x40
Oct 18 05:08:36 btrfs kernel: [<ffffffffa01a2540>]
start_transaction+0x1e0/0x2b0 [btrfs]
Oct 18 05:08:36 btrfs kernel: [<ffffffffa01a2665>]
btrfs_join_transaction+0x15/0x20 [btrfs]
Oct 18 05:08:36 btrfs kernel: [<ffffffffa01ad360>]
btrfs_dirty_inode+0x50/0x160 [btrfs]
Oct 18 05:08:36 btrfs kernel: [<ffffffff8115631f>]
__mark_inode_dirty+0x3f/0x200
Oct 18 05:08:36 btrfs kernel: [<ffffffff81148bf5>] touch_atime+0x115/0x150
Oct 18 05:08:36 btrfs kernel: [<ffffffff81142520>] ? sys_ioctl+0xb0/0xb0
Oct 18 05:08:36 btrfs kernel: [<ffffffff811426ce>] vfs_readdir+0xce/0xe0
Oct 18 05:08:36 btrfs kernel: [<ffffffff81142849>] sys_getdents+0x89/0xf0
Oct 18 05:08:36 btrfs kernel: [<ffffffff814b19ab>]
system_call_fastpath+0x16/0x1b
next reply other threads:[~2011-10-18 13:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 13:25 Jim [this message]
2011-10-18 13:31 ` ls hangs filesystem Josef Bacik
2011-10-18 13:47 ` Jim
2011-10-18 13:49 ` Sander
2011-10-18 13:50 ` Jim
2011-10-18 14:03 ` Jim
2011-10-18 14:04 ` Josef Bacik
2011-10-18 14:08 ` Jim
2011-10-18 14:09 ` Josef Bacik
2011-10-18 14:10 ` Jim
2011-10-18 14:26 ` Jim
2011-10-18 14:08 ` Sander
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=4E9D7E5A.2010403@webstarts.com \
--to=jim@webstarts.com \
--cc=linux-btrfs@vger.kernel.org \
/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