From: Philippe Cerfon <philcerf@googlemail.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] when to vgscan/pvscan/lvscan
Date: Wed, 23 Jun 2010 13:46:49 +0200 [thread overview]
Message-ID: <AANLkTinqbHHCIv4YLoBGnJ0xHuA0psm3j50bwTkY4oLS@mail.gmail.com> (raw)
(seems that this did not came through the first time?!)
Hi.
(Talking always about lvm2...)
Is there a real technical difference between pvscan, vgscan and lvscan?
I mean as far as I understand one always needs all information about
PVs,VGs and LVs in order to get the later.
So apart from different textual "debug" output, do all the same, i.e.
scanning over all configured block devices, looking for PVs and
scanning their VG-descriptors in order to get the information about al
LVs?
Is there ever the need to rund pvscan/vgscan/lvscan manually and if so
in which cases? I mean the vgscan manpage says that this happens
automatically in lvm2, so if I e.g. have my init-scripts and want to
make the LVs available, is it generally enough to do
vgchange -an
or can there be cases when the preceding vgscan is still required?
Thanks,
Philippe.
next reply other threads:[~2010-06-23 11:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 11:46 Philippe Cerfon [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-06-30 20:34 [linux-lvm] when to vgscan/pvscan/lvscan Philippe Cerfon
2010-06-30 20:57 ` Alasdair G Kergon
2010-07-01 23:24 Philippe Cerfon
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=AANLkTinqbHHCIv4YLoBGnJ0xHuA0psm3j50bwTkY4oLS@mail.gmail.com \
--to=philcerf@googlemail.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).