From: Alasdair G Kergon <agk@redhat.com>
To: Philippe Cerfon <philcerf@yahoo.com>
Cc: linux-lvm@redhat.com
Subject: Re: [linux-lvm] when to vgscan/pvscan/lvscan
Date: Wed, 30 Jun 2010 21:57:29 +0100 [thread overview]
Message-ID: <20100630205728.GR23989@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <180678.70848.qm@web120413.mail.ne1.yahoo.com>
The code is supposed to auto-detect changes, but there are still
(mostly obscure) ways that confuse it.
The safest approach if you want to remove the vgscan at boot is to
specify the precise VGs you want to activate by name on the vgchange
command line instead of letting it default to 'all'.
So 'vgchange -ay root_vg home_vg' etc. instead of 'vgchange -ay'.
Then it knows what VGs are supposed to be there, and if it didn't think
it needed to scan but doesn't see one or more of them that'll be enough
to trigger the scan.
Alasdair
next prev parent reply other threads:[~2010-06-30 20:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-30 20:34 [linux-lvm] when to vgscan/pvscan/lvscan Philippe Cerfon
2010-06-30 20:57 ` Alasdair G Kergon [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-07-01 23:24 Philippe Cerfon
2010-06-23 11:46 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=20100630205728.GR23989@agk-dp.fab.redhat.com \
--to=agk@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=philcerf@yahoo.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).