From: "Stuart D. Gathman" <stuart@bmsi.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Problems resizing physical volume
Date: Wed, 14 Apr 2010 17:57:05 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.1004141752130.14791@bmsred.bmsi.com> (raw)
In-Reply-To: <20100414212845.GD13021@agk-dp.fab.redhat.com>
On Wed, 14 Apr 2010, Alasdair G Kergon wrote:
> On Wed, Apr 14, 2010 at 05:12:31PM -0400, Phillip Susi wrote:
> > Grub2.
>
> Dangerous code which can mis-process configurations it does not recognise.
> I advise people not to use it unless they've tested their specific metadata
> gets processed by it correctly.
AIX had a clever way of integrating their LVM with boot. There was a specially
marked boot LV that was required to have exactly one extent, and was not
allowed to move (without updating the boot code). The "boot" flag
caused the userspace tools to prevent operations that might leave the
system unbootable.
This reduces LVM to the equivalent of a partition as far as the
boot code is concerned.
--
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-04-14 21:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 9:42 [linux-lvm] Problems resizing physical volume Avi Kivity
2010-04-14 14:47 ` Phillip Susi
2010-04-14 14:59 ` Avi Kivity
2010-04-14 15:04 ` Avi Kivity
2010-04-14 15:14 ` Phillip Susi
2010-04-14 20:05 ` Stuart D. Gathman
2010-04-14 21:12 ` Phillip Susi
2010-04-14 21:28 ` Alasdair G Kergon
2010-04-14 21:57 ` Stuart D. Gathman [this message]
2010-04-14 22:27 ` Alasdair G Kergon
2010-04-24 1:39 ` Ron Johnson
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.1004141752130.14791@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).