From: Joe Thornber <thornber@btconnect.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] what happens when hdX get hdY in a VG
Date: Wed, 18 Jul 2001 11:59:43 +0100 [thread overview]
Message-ID: <20010718115943.A712@btconnect.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0107181226430.17377-100000@diablo.unixag-zw.fh-kl.de>; from jovi@unixag-zw.fh-kl.de on Wed, Jul 18, 2001 at 12:48:09PM +0200
On Wed, Jul 18, 2001 at 12:48:09PM +0200, Oliver Jovic wrote:
> Hi, :-)
>
> well what happens when i have a VG build out of /dev/hd[e-h]1 (4
> harddrives) and build in now a additional IDE controller and 4
> additional harddrives and this new IDE controller wants these
> driverletters now, so /dev/hde gets /dev/hdi and so on? Will a vgscan
> in the startupscripts detect the right drives anyways due to the headers
> of each harddisk and build the VG/LV as it was before just with different
> driveletters?
>
> If not, what do i need to do? Havent found much info about it, but well
> must be also be honest, hadnt much time to look for it. ;-/ Sorry if
> somebody asked this already.
vgscan should do the right thing.
- Joe
next prev parent reply other threads:[~2001-07-18 10:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-17 21:52 [linux-lvm] HUGE LVM log file Gonyou, Austin
2001-07-18 0:00 ` Wolfgang Weisselberg
2001-07-18 8:22 ` Joe Thornber
2001-07-18 8:48 ` Benoit SERRA
2001-07-18 9:33 ` Joe Thornber
2001-07-18 19:23 ` Ragnar Kjørstad
2001-07-18 22:22 ` lembark
2001-07-18 9:46 ` Adam Cioccarelli
[not found] ` <Pine.LNX.4.33.0107181141480.25686-100000@vie-ac.office.ece tra.com>
2001-07-18 9:47 ` Benoit SERRA
2001-07-18 10:48 ` [linux-lvm] what happens when hdX get hdY in a VG Oliver Jovic
2001-07-18 10:59 ` Joe Thornber [this message]
2001-07-18 13:29 ` [linux-lvm] HUGE LVM log file Iain Campbell
2001-07-18 17:02 ` Steven Lembark
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=20010718115943.A712@btconnect.com \
--to=thornber@btconnect.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