From: "Stuart D. Gathman" <stuart@bmsi.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Adding a disk to expand an existing logical volume
Date: Wed, 19 May 2010 15:34:38 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.1005191524400.29583@bmsred.bmsi.com> (raw)
In-Reply-To: <1274289803.16893.12@raydesk1.bettercgi.com>
On Wed, 19 May 2010, Ray Morris wrote:
> It's also useful during the boot process. If, for example, you
> later add another disk, this disk might become sdd, where it used to
> be sdc. That can confuse initrd and friends and result in an
> unbootable system. On almost every machine where I've skipped
> creating partitions for RAID or LVM, this kind of thing has come
> back to bite me later - maybe years later. Now, I always create
> "Linux LVM" partitions for LVM and "Linux raid autodetect" partitions
> for RAID. It makes booting an recovering much more reliable in
> case of changes or problems.
PVs are identified by UUID. It doesn't matter whether they change
names. And changing names from sdc1 to sdd1 is just as bad as changing
names from sdc to sdd.
However, you are correct that the default device searching rules used by
lvm might work correctly with a Linux LVM labeled partition where they might
otherwise skip a device. If you aren't familiar with lvm.conf, then
using labeled partitions is a safer course. (initrd uses a copy
of lvm.conf to find PVs so it can activate the volume group of the
root filesystem if necessary.)
--
Stuart D. Gathman <stuart@bmsi.com>
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.
next prev parent reply other threads:[~2010-05-19 19:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 15:43 [linux-lvm] Adding a disk to expand an existing logical volume kevin
2010-05-19 15:58 ` Digimer
2010-05-19 16:09 ` kevin
2010-05-19 16:28 ` Digimer
2010-05-19 16:24 ` Michael Guntsche
2010-05-19 22:28 ` Ron Johnson
2010-05-20 5:24 ` Luca Berra
2010-05-20 11:21 ` Bryn M. Reeves
2010-05-19 16:26 ` Malahal Naineni
2010-05-19 16:37 ` kevin
2010-05-19 16:46 ` Digimer
2010-05-19 17:05 ` Bryn M. Reeves
2010-05-19 16:51 ` Stuart D. Gathman
2010-05-19 16:57 ` Digimer
2010-05-19 17:07 ` kevin
2010-05-19 17:09 ` kevin
2010-05-19 17:28 ` Richard Shaw
2010-05-19 17:35 ` Ray Morris
2010-05-19 18:25 ` Digimer
2010-05-19 17:23 ` Ray Morris
2010-05-19 19:34 ` Stuart D. Gathman [this message]
2010-05-28 23:16 ` Ray Morris
2010-05-19 17:03 ` Bryn M. Reeves
2010-05-19 15:58 ` Richard Jerrido
2010-05-19 16:12 ` kevin
2010-05-19 16:46 ` Stuart D. Gathman
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=Pine.LNX.4.64.1005191524400.29583@bmsred.bmsi.com \
--to=stuart@bmsi.com \
--cc=linux-lvm@redhat.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).