From: "Busby.Cheung" <chaimvy@163.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] lvm2's problem or device-mapper's?
Date: Wed, 10 Mar 2010 14:34:48 +0800 (CST) [thread overview]
Message-ID: <9a0cbd.10a11.12746c85c40.Coremail.chaimvy@163.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 691 bytes --]
Hi All,
I used 'lvcreate' cmd to create a logical-volume named 'lv-test', belongs to volume group 'vg00'.
Then I gave the lv-test big IO like:'dd if=/dev/zero of=/dev/mapper/lv-test bs=4K'. while it was in this big IO, I use 'lvcreate' cmd to create a new lv using lv-test's vg 'vg00'. it take a long time to do it. I found it finish util the 'dd' ended.
Is it caused by some functions like 'suspend' in VG, the IO suspend can't be done in a very quick way?
I don't know what cause the problem, 'lvcreate' a new LV very slowly while big IO on another LV in the same VG.
Anyone can help me? Thank you very much.
best regards,
Bubsy Cheung
[-- Attachment #2: Type: text/html, Size: 1085 bytes --]
reply other threads:[~2010-03-10 6:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9a0cbd.10a11.12746c85c40.Coremail.chaimvy@163.com \
--to=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).