Linux LVM users
 help / color / mirror / Atom feed
From: Don Buchholz <buchholz@easystreet.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM and hardware device re-ordering?
Date: Fri, 30 Apr 2004 10:43:42 -0700	[thread overview]
Message-ID: <4092904E.1010101@easystreet.com> (raw)
In-Reply-To: <20040430162957.GA8717@null.msp.redhat.com>

Thanks, AJ.

May I propose this question for inclusion in the LVM HOWTO FAQ chapter?

- Don

AJ Lewis wrote:

>On Fri, Apr 30, 2004 at 08:55:32AM -0700, Don Buchholz wrote:
>  
>
>>The one nagging question in my mind is:
>>
>> How resilient is LVM to a sudden renumbering of
>> physical hard disks?
>>
>>Assume no disks have actually failed, just that a new disk
>>gets added and suddenly all the LVM drives get notched up
>>a drive letter. 
>>    
>>
>
>It's fine.  Each disk (PV) is labeled with a UUID, which uniquely identifies
>it to the system.  'vgscan' identifies this after a new disk is added that
>changes your drive numbering.  Most distros run vgscan in the lvm startup
>scripts to cope with this on reboot after a hardware addition.  If you're
>doing a hot-add, you'll have to run this by hand I think.  OTOH, if your vg
>is activated and being used, the renumbering should not affect it at all.
>It's only the activation that needs the identifier, and the worst case
>scenario is that the activation will fail without a vgscan with a complaint
>about a missing PV.
>
>Regards,
>  
>
>------------------------------------------------------------------------
>
>_______________________________________________
>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/
>

  reply	other threads:[~2004-04-30 17:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-30 15:55 [linux-lvm] LVM and hardware device re-ordering? Don Buchholz
2004-04-30 16:29 ` AJ Lewis
2004-04-30 17:43   ` Don Buchholz [this message]
2004-05-03 13:51     ` AJ Lewis

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=4092904E.1010101@easystreet.com \
    --to=buchholz@easystreet.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