From: Andreas Dilger <adilger@turbolabs.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] invalidate: busy buffer
Date: Mon Dec 17 01:30:02 2001 [thread overview]
Message-ID: <20011217003242.K855@lynx.no> (raw)
In-Reply-To: <20011216205044.F26924@tiger.bigcats.invalid>; from weissel@netcologne.de on Sun, Dec 16, 2001 at 08:50:44PM +0100
On Dec 16, 2001 20:50 +0100, Wolfgang Weisselberg wrote:
> BTW, is there a good reason to run vgscan on boot time every
> time? I have had more sorrow than joy with that. If my
> vg's really changed, I can always run it from the (non-LVM)
> / which will come up, even if only as an emergency system.
It is only really useful if your drive mappings are likely to change
(i.e. adding SCSI drives, or re-arranging your IDE drives). Otherwise,
it is not necessary to run vgscan at boot.
IMHO, the concept of running "vgscan" at boot is flawed, because it
re-builds the entire _VG_ setup each time it is run. I would much
rather only rebuild the _PV_ setup on each boot (which is the only
likely thing to change between reboots), and leave the VG setup alone.
It should be up to the sysadmin to change the VG config.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2001-12-17 1:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-14 13:14 [linux-lvm] invalidate: busy buffer Petro
2001-12-16 14:38 ` Wolfgang Weisselberg
2001-12-16 15:50 ` Ulrich Wiederhold
2001-12-16 21:12 ` Wolfgang Weisselberg
2001-12-17 2:56 ` Ulrich Wiederhold
2001-12-17 7:53 ` Todd M. Roy
2001-12-16 18:47 ` Petro
2001-12-17 1:30 ` Andreas Dilger [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-07 3:36 [linux-lvm] Invalidate: Busy Buffer mikyy
2001-11-07 5:42 ` Ulrich Wiederhold
2001-11-07 7:37 ` Heinz J . Mauelshagen
2001-11-07 8:53 ` joan
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=20011217003242.K855@lynx.no \
--to=adilger@turbolabs.com \
--cc=linux-lvm@sistina.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).