From: Christoph Hellwig <hch@caldera.de>
To: Peter Samuelson <peter@cadcamlab.org>
Cc: lvm-devel@sistina.com, linux-kernel@vger.kernel.org
Subject: Re: [lvm-devel] *** ANNOUNCEMENT *** LVM 0.9.1 beta5 available at www.sistina.com
Date: Thu, 22 Feb 2001 12:53:15 +0100 [thread overview]
Message-ID: <20010222125315.A17011@caldera.de> (raw)
In-Reply-To: <20010221180035.N25927@athlon.random> <200102211718.SAA25997@ns.caldera.de> <20010221221225.B21010@cadcamlab.org> <20010222104603.A1992@caldera.de> <14996.61315.647325.114938@wire.cadcamlab.org>
In-Reply-To: <14996.61315.647325.114938@wire.cadcamlab.org>; from peter@cadcamlab.org on Thu, Feb 22, 2001 at 04:52:51AM -0600
On Thu, Feb 22, 2001 at 04:52:51AM -0600, Peter Samuelson wrote:
>
> [Peter Samuelson]
> > > How often do you run MAKEDEV or vgscan?
>
> [Christoph Hellwig]
> > On every bootup, _before_ doing mount -a
>
> A mere 'vgchange -ay' works fine for *my* boot processes. Is there a
> particular reason to do 'vgscan' every time? (I'm not arguing -- just
> wondering.)
It is that what is suggested by the LVM crew. I have also tried to use
it without vgscan - it work then and whenn, but not 100% percent reliable.
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
Whip me. Beat me. Make me maintain AIX.
prev parent reply other threads:[~2001-02-22 11:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010220224907.D21281@srv.sistina.com>
2001-02-20 22:42 ` [lvm-devel] *** ANNOUNCEMENT *** LVM 0.9.1 beta5 available at www.sistina.com Andrea Arcangeli
2001-02-21 0:31 ` Andreas Dilger
2001-02-21 1:12 ` Andrea Arcangeli
2001-02-21 3:49 ` Richard Gooch
2001-02-21 17:00 ` Andrea Arcangeli
2001-02-21 17:03 ` Richard Gooch
2001-02-21 17:18 ` Christoph Hellwig
2001-02-22 4:12 ` Peter Samuelson
2001-02-22 9:46 ` Christoph Hellwig
2001-02-22 10:52 ` Peter Samuelson
2001-02-22 11:53 ` Christoph Hellwig [this message]
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=20010222125315.A17011@caldera.de \
--to=hch@caldera.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lvm-devel@sistina.com \
--cc=peter@cadcamlab.org \
/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