Hi ALL,
When I used the lvcreate cmd in my system, it blocked for a long time. My OS kernel version is linux-2.6.29, is there any bug?
Here is the mesg:
INFO: task lvcreate:30225 blocked for more than 480 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
lvcreate D ffff880028088780 0 30225 25700
ffff88013e02a100 0000000000000086 0000000000000000 0000000000000000
00000000000000d0 ffff880124879910 ffff880124879c70 00000001000aaa4a
ffffffffffffffff ffffffffffffffff ffffffffffffffff 7fffffffffffffff
Call Trace:
[<ffffffff804d4d5d>] io_schedule+0x5d/0x9e
[<ffffffff802bfff5>] __blockdev_direct_IO+0x8a4/0xa3b
[<ffffffff80272842>] __filemap_fdatawrite_range+0x54/0x5e
[<ffffffff802bee5e>] blkdev_direct_IO+0x45/0x4a
[<ffffffff802bed84>] blkdev_get_blocks+0x0/0x95
[<ffffffff80272c28>] generic_file_direct_write+0xd2/0x18b
[<ffffffff80272f65>] __generic_file_aio_write_nolock+0x284/0x3a5
[<ffffffff802734d7>] generic_file_aio_read+0xe1/0x539
[<ffffffff80273138>] generic_file_aio_write_nolock+0x34/0x80
[<ffffffff8029d6db>] do_sync_write+0xc9/0x10c
[<ffffffff803958e4>] tty_put_char+0x2b/0x2d
[<ffffffff80249396>] autoremove_wake_function+0x0/0x2e
[<ffffffff80326a0c>] selinux_file_permission+0x5a/0x120
[<ffffffff8029ddd7>] vfs_write+0xad/0x136
[<ffffffff8029e2f4>] sys_write+0x45/0x6e
[<ffffffff8020bedb>] system_call_fastpath+0x16/0x1b
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
lvcreate D ffff880028088780 0 30225 25700
ffff88013e02a100 0000000000000086 0000000000000000 0000000000000000
00000000000000d0 ffff880124879910 ffff880124879c70 00000001000aaa4a
ffffffffffffffff ffffffffffffffff ffffffffffffffff 7fffffffffffffff
Call Trace:
[<ffffffff804d4d5d>] io_schedule+0x5d/0x9e
[<ffffffff802bfff5>] __blockdev_direct_IO+0x8a4/0xa3b
[<ffffffff80272842>] __filemap_fdatawrite_range+0x54/0x5e
[<ffffffff802bee5e>] blkdev_direct_IO+0x45/0x4a
[<ffffffff802bed84>] blkdev_get_blocks+0x0/0x95
[<ffffffff80272c28>] generic_file_direct_write+0xd2/0x18b
[<ffffffff80272f65>] __generic_file_aio_write_nolock+0x284/0x3a5
[<ffffffff802734d7>] generic_file_aio_read+0xe1/0x539
[<ffffffff80273138>] generic_file_aio_write_nolock+0x34/0x80
[<ffffffff8029d6db>] do_sync_write+0xc9/0x10c
[<ffffffff803958e4>] tty_put_char+0x2b/0x2d
[<ffffffff80249396>] autoremove_wake_function+0x0/0x2e
[<ffffffff80326a0c>] selinux_file_permission+0x5a/0x120
[<ffffffff8029ddd7>] vfs_write+0xad/0x136
[<ffffffff8029e2f4>] sys_write+0x45/0x6e
[<ffffffff8020bedb>] system_call_fastpath+0x16/0x1b
I don't know whether it is the kernel's scheduling bug or the lvm2's bug, anyone knows?
Best Wishes!
_______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/