From: Wolfgang Weisselberg <weissel@netcologne.de>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] invalidate: busy buffer
Date: Sun Dec 16 21:12:02 2001 [thread overview]
Message-ID: <20011217035359.A4880@tiger.bigcats.invalid> (raw)
In-Reply-To: <20011216215414.GB12889@sky.net>; from U.Wiederhold@gmx.net on Sun, Dec 16, 2001 at 10:54:14PM +0100
Hi, Ulrich!
Ulrich Wiederhold (U.Wiederhold@gmx.net) wrote 26 lines:
> * Wolfgang Weisselberg <weissel@netcologne.de> [011216 20:50]:
> > 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.
> Ok, but you need to run vgscan && vgchange -ay every time you wanna use
> your LVM-drives, and I think that's normally every time you boot your
> PC.
Funny, my PC boots and mounts the LVs even though I commented
out vgscan entirely in the boot process. vgchange is another
thing, though...
> But... I add them
> to /etc/rcS.d/S99local incl. the mount command.
Faaar to late -- considering that all the daemons start up early
and need fancy things like /usr, /var and sometimes /tmp ..
-Wolfgang
next prev parent reply other threads:[~2001-12-16 21:12 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 [this message]
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
-- 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=20011217035359.A4880@tiger.bigcats.invalid \
--to=weissel@netcologne.de \
--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 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.