linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Luca Berra <bluca@comedia.it>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Adding a disk to expand an existing logical volume
Date: Thu, 20 May 2010 07:24:15 +0200	[thread overview]
Message-ID: <20100520052415.GA27154@maude.comedia.it> (raw)
In-Reply-To: <4BF4660C.60307@cox.net>

On Wed, May 19, 2010 at 05:28:28PM -0500, Ron Johnson wrote:
> On 05/19/2010 11:24 AM, Michael Guntsche wrote:
>> On 2010.05.19 11:58:03 , Digimer wrote:
>>> On 10-05-19 11:43 AM, kevin wrote:
>>>> Howdy,
>>>>
>>>> (fdisk+mkfs+pvcreate+vgextend+lvextend) is the right way to go about adding
>>>
>>> The mkfs isn't supposed to be there, just set the new drive's
>>> partition to type '8e' (Linux LVM).
>> Or use the full device without any partition at all.
>>
>
> I wonder if this will have any adverse affects on drives with 4KB sectors?
it depends
on a disk with 4k sector, using the whole device is more likely to have
a correct alignment (0 is a multiple of 4k)

on a disk with 4k sector and the first sector shifted (some drives have
a jumper to achieve this, it might be called something like "XP
compatibility") using the whole device, or anything not aligned to
63x512byte will result in unaligned data.

afair recent kernels should expose the alignment and sector size under
/sys/block/..., (if the drive exposes that info and does not lie, that
is.) and fdisk/parted/lvm/md should correctly align data start.

On a personal note, i really despise partition tables, it is a broken
design from the early eighties, we should be able to move on. If you
must use a GPT partition, at least it has a backup block.

L.


-- 
Luca Berra -- bluca@comedia.it
         Communication Media & Services S.r.l.
  /"\
  \ /     ASCII RIBBON CAMPAIGN
   X        AGAINST HTML MAIL
  / \

  reply	other threads:[~2010-05-20  5:24 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 [this message]
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
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=20100520052415.GA27154@maude.comedia.it \
    --to=bluca@comedia.it \
    --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).