From: Ray Morris <support@bettercgi.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 12:23:23 -0500 [thread overview]
Message-ID: <1274289803.16893.12@raydesk1.bettercgi.com> (raw)
In-Reply-To: <4BF41884.4080000@alteeve.com> (from linux@alteeve.com on Wed May 19 11:57:40 2010)
>> The partition table, although otherwise useless for LVM (and a pain
>> when
>> trying to align PPs to some lower lever boundary), does serve the
>> purpose
>> of telling other PC operating systems that there is something there.
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.
> a pain when trying to align PPs to some lower lever boundary
A trick to avoid all of the math of alignment is to just
start the first partition on sector 512 every time, rather
than sector 63. Sometimes you can save a few KB by doing the
math and finding a lower offset, but it's just a few KB -
who cares. That works because 512 sectors is 256KB - a
perfect multiple of any RAID size you might use.
--
Ray Morris
support@bettercgi.com
Strongbox - The next generation in site security:
http://www.bettercgi.com/strongbox/
Throttlebox - Intelligent Bandwidth Control
http://www.bettercgi.com/throttlebox/
Strongbox / Throttlebox affiliate program:
http://www.bettercgi.com/affiliates/user/register.php
On 05/19/2010 11:57:40 AM, Digimer wrote:
> On 10-05-19 12:51 PM, Stuart D. Gathman wrote:
>> On Wed, 19 May 2010, kevin wrote:
>>
>>>> If I were you, I would not bother with partition(s). I will add the
>>>> whole disk to LVM.
>>>
>>> I intend for the entire disk to be used -- so I should just skip
>>> the fdisk
>>> step?
>>
>> Yes, just do the pvcreate directly on /dev/sdc (instead of
>> /dev/sdc1).
>>
>> I would only recommend this if the drive is permanently attached to
>> your
>> server. If there is any possibility of it getting moved to another
>> system,
>> especially another OS, it is likely to appear "unformatted" and the
>> other
>> OS will offer to create a partition table, etc, destroying the data.
>> The partition table, although otherwise useless for LVM (and a pain
>> when
>> trying to align PPs to some lower lever boundary), does serve the
>> purpose
>> of telling other PC operating systems that there is something there.
>
> There ya go, I learn something new every day. :)
>
>--
> Digimer
> E-Mail: linux@alteeve.com
> AN!Whitepapers: http://alteeve.com
> Node Assassin: http://nodeassassin.org
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
next prev parent reply other threads:[~2010-05-19 17:23 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 [this message]
2010-05-19 19:34 ` Stuart D. Gathman
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=1274289803.16893.12@raydesk1.bettercgi.com \
--to=support@bettercgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.