From: Ray Morris <support@bettercgi.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: chaimvy@163.com
Subject: Re: [linux-lvm] why 'lvcreate' command blocked?
Date: Sat, 2 Jul 2011 01:30:30 -0500 [thread overview]
Message-ID: <20110702013030.443f3d8b@bettercgi.com> (raw)
In-Reply-To: <5d9860.22c.130e47547b4.Coremail.chaimvy@163.com>
Please let me know if you figure it out. I have a server
with a similar problem which persists even after changing
virtually every component of the system. One hint I learned
is that it can at times hang for serveral hours and then
proceed. Just because it's been several minutes does not
necesarily mean a 180 mile trip to the datacenter.
--
Ray Morris
support@bettercgi.com
Strongbox - The next generation in site security:
http://www.bettercgi.com/strongbox/
Throttlebox - Intelligent Bandwidth Control
http://www.bettercgi.com/throttlebox/
Strongbox / Throttlebox affiliate program:
http://www.bettercgi.com/affiliates/user/register.php
On Fri, 1 Jul 2011 14:49:09 +0800 (CST)
"Busby.Cheung" <chaimvy@163.com> wrote:
> 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
>
> I don't know whether it is the kernel's scheduling bug or the
> lvm2's bug, anyone knows?
> Best Wishes!
>
>
>
next prev parent reply other threads:[~2011-07-02 6:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 6:49 [linux-lvm] why 'lvcreate' command blocked? Busby.Cheung
2011-07-01 18:37 ` Stuart D. Gathman
2011-07-02 6:30 ` Ray Morris [this message]
2011-07-04 2:33 ` Busby.Cheung
2011-07-04 2:39 ` Busby.Cheung
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=20110702013030.443f3d8b@bettercgi.com \
--to=support@bettercgi.com \
--cc=chaimvy@163.com \
--cc=linux-lvm@redhat.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;
as well as URLs for NNTP newsgroup(s).