Skip to contentSkip to conversation

lvm2 specificiation

linux-lvm Alasdair G Kergon 6 participants 6 messages Feb 5, 2009 – Feb 6, 2009

lore
Share & tools
lore
#0 lore raw
Quoted 4 lines · Vinay Srini

I have a requirement to mount multiple volume groups with the same name (VolGroup00, as that is the most popular default name), without first using vgrename (because something might go wrong, and I may not be able to restore the name back).

It was an early design decision that every VG on a system should have a different name. Departures from that won't get supported - because it's so simple to choose different names!

Alasdair

Signature · 1 line
[email protected]
#1 lore raw
Quoted 6 lines · Alasdair G Kergon
Quoted 1 line · Vinay Srini

I have a requirement to mount multiple volume groups with the same name (VolGroup00, as that is the most popular default name), without first using vgrename (because something might go wrong, and I may not be able to restore the name back).

It was an early design decision that every VG on a system should have a different name. Departures from that won't get supported - because it's so simple to choose different names!

How do you move drives around among machines then, if they have been created with the default names that will conflict?

Signature · 2 lines
  Les Mikesell
    [email protected]
#2 lore raw
Quoted 10 lines · Les Mikesell
Quoted 6 lines · Alasdair G Kergon
Quoted 1 line · Vinay Srini

I have a requirement to mount multiple volume groups with the same name (VolGroup00, as that is the most popular default name), without first using vgrename (because something might go wrong, and I may not be able to restore the name back).

It was an early design decision that every VG on a system should have a different name. Departures from that won't get supported - because it's so simple to choose different names!

How do you move drives around among machines then, if they have been created with the default names that will conflict?

These are flat files mounted in a directory across the network. Which when accessed, gets bytes across the network. (mounted using fuse libs)

eg. if the flat file is located in /mnt/over-network/flat,

# losetup -f --show /mnt/over-network/flat
/dev/loop0
# vgscan (this will find my VolGroup00)
# .. and so on

One example is mounting virtual machine drives from the virtual server on to my desktop. In this case, i would like to perform some operations on the drive (copy from/to etc), and unmount.

Is there an RFC for the lvm design that I could read throught to better understand this?

Vinay.

#3 lore raw
In reply to Les Mikesell
Quoted 10 lines · Les Mikesell
Quoted 6 lines · Alasdair G Kergon
Quoted 1 line · Vinay Srini

I have a requirement to mount multiple volume groups with the same name (VolGroup00, as that is the most popular default name), without first using vgrename (because something might go wrong, and I may not be able to restore the name back).

It was an early design decision that every VG on a system should have a different name. Departures from that won't get supported - because it's so simple to choose different names!

How do you move drives around among machines then, if they have been created with the default names that will conflict?

Using the oft-posted directions for changing the VG name and UUID.

Regards,
Bryn.

#4 lore raw
In reply to Les Mikesell
Quoted 7 lines · Les Mikesell
Quoted 5 lines

It was an early design decision that every VG on a system should have a different name. Departures from that won't get supported - because it's so
simple to choose different names!

How do you move drives around among machines then, if they have been created with the default names that will conflict?

SAN based snapshots are the legitimate reason to wish for multiple VGs with the same name. However, it is simpler all around if there was an easy way to relabel SAN snapshots before the duplicate names (and VGIDs) cause trouble.

Apart from SAN snapshots, my rule of thumb is that local fixed drives are always called "rootvg". All removeable, SAN, or other drives that are likely to logically or physically move between machines get unique VG names. In the rare event I need to mount a rootvg from a failed machine on a working machine (has happened only once), I boot from CD to rename it (and the unique VGIDs make this doable).

begin:vcard
fn:Stuart Gathman
n:Gathman;Stuart
org:Business Management Systems, Inc adr;dom:;;4001 Williamsburg Court;Fairfax;VA;22032 email;internet:[email protected] tel;work:703 591-0911
tel;fax:703 591-6154
tel;home:703 378-9641
note:AIM: SDGathman
x-mozilla-html:FALSE
url:http://bmsi.com
version:2.1
end:vcard

#5 lore raw
In reply to Les Mikesell
Quoted 2 lines

How do you move drives around among machines then, if they have been created with the default names that will conflict?

Never use the default names?

Stefan