From: Jun'ichi Nomura <j-nomura@ce.jp.nec.com>
To: lvm-devel@redhat.com
Subject: Filtering out LVs?
Date: Tue, 29 Mar 2011 20:08:23 +0900 [thread overview]
Message-ID: <4D91BDA7.2030003@ce.jp.nec.com> (raw)
Hi,
LVM2 commands scan /dev for metadata read-in and validation.
By default, it includes DM devices.
On the other hand, LV deactivation checks its open count
and fails if it's open.
So there is a race that one of multiple vgchange instances prevents other;
"vgchange -an vg0" might fail to deactivate the VG if "vgchange -an vg1"
opens vg0/lv0 at the very time for scanning.
E.g. try this:
From one console,
# while true; do vgscan; done
and from other console,
# while true; do vgchange -ay $VG; vgchange -an $VG || break; done
While device filter can be configured to avoid LV devices,
and also someone may want to use LV as PV,
it seems inconvenient default behavior.
Does it make sense to add a filter to avoid LVs?
(It has to cope with multiple udev-oriented aliases...)
--
Jun'ichi Nomura, NEC Corporation
next reply other threads:[~2011-03-29 11:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 11:08 Jun'ichi Nomura [this message]
2011-03-31 6:33 ` Filtering out LVs? Alasdair G Kergon
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=4D91BDA7.2030003@ce.jp.nec.com \
--to=j-nomura@ce.jp.nec.com \
--cc=lvm-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.