[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Mounting LVM sub-partitions - SOLVED


  • To: Kevin DeGraaf <kevin@xxxxxxxxxxxx>
  • From: Nico Kadel-Garcia <nkadel@xxxxxxxxx>
  • Date: Sat, 11 Aug 2007 07:42:42 +0100
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 10 Aug 2007 23:42:29 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=hzyySzU4Prtdnvt9BtDzhMPHv+4QxFqCrGDVVHUH3FldpPRlB/PkEe/H8vSHUAo2AvTx3dpohjZKG/m1qd/+q9ex+5itoxP+LkCmGGY1LEBDFK9EGHfafuAq4KBQnTs3WM+0T2pafwKrgjOZzSgu+NgAXxjXWPhalk+yaPVBUfg=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Kevin DeGraaf wrote:
have a closer look to kpartx as a part of the multimapper-tools:

That worked, thanks.

For the benefit of anyone searching the archives for this issue:

  # apt-get install multipath-tools
  # kpartx -a /dev/vg0/lv0
  # mount /dev/mapper/lv0p1 /mnt/foo

I'm a bit surprised that it didn't follow the format of the existing
nodes (e.g. /dev/mapper/vg0-lv0--p1).  Doing it the naive way allows
collisions between similarly-named LVs in different VGs.  Oh well.  :-)
You noticed that! Yeah the syntax of device naming there is a bit interesting. It makes it important to name the partitions for your DomU's in ways that will not naturally collide. Me, I create a specific volume group for them called something like XENDISK and use names for the individual DomU's such as "DOMU01", "DOMU02", etc. That helps avoid collisions.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.