From: Goetz Bock <bock@blacknet.de>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] How does LVM handle physical changes?
Date: Wed, 3 Oct 2001 01:41:44 +0200 [thread overview]
Message-ID: <20011003014144.B10834@dragon.blacknet.de> (raw)
In-Reply-To: <20011002232426.A1175@balu.kawo2.rwth-aachen.de>; from mdobel@kawo2.rwth-aachen.de on Tue, Oct 02, 2001 at 11:24:26PM +0200
[-- Attachment #1: Type: text/plain, Size: 597 bytes --]
On Tue, Oct 02 '01 at 23:24, Markus Dobel wrote:
> Can LVM handle physical changes of my system, like plugging the PVs
> from one controller to another (so the physical device path changes
> e.g. from /dev/hdb to /dev/hdf)?
Yep, as long as the geometry stays the same. I even moved some disks
from /dev/hd[ce] to /dev/sd[ab] and LVM worked like a charm.
(I used a 3ware IDE controller with /dev/sd[ab] configurated as BOD. It
is an IDE RAID that appears to the system as a SCSI controller)
--
Goetz Bock IT Consultant
Dipl.-Inf. Univ.
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2001-10-02 23:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-02 21:24 [linux-lvm] How does LVM handle physical changes? Markus Dobel
2001-10-02 23:41 ` Goetz Bock [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=20011003014144.B10834@dragon.blacknet.de \
--to=bock@blacknet.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 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).