From: Kenny Lussier kluss...@gmail.com
To: Jeffrey O'brien jobr...@expertserver.com
CC: gnhlug-disc...@gnhlug.org
Date: 3/18/2009 7:44 PM
Subject:Re: Labeling Multipath drives
On Wed, Mar 18, 2009 at 9:54 AM, Jeffrey O'brien
jobr...@expertserver.comwrote:
Kenny, you
Hi All,
I currently have a failover cluster with a shared iSCSI disk. It is just
an ext3 partition that has a disk label. If the primary box drops, the
backup box (through the magic of clustering), knows that it needs to mount
the disk where LABEL=HA_DISK. However, I am soon going to be moving
2009/3/18 Kenny Lussier kluss...@gmail.com:
I have is that if I use e2label on the partition that ends up in
/dev/mapper, I can't mount by label. I get an error saying Multiple drives
found with identical label. Does anyone know how to work around this?
I was going to suggest mounting by
2009/3/18 mark prg...@gmail.com
2009/3/18 Kenny Lussier kluss...@gmail.com
Hi All,
I currently have a failover cluster with a shared iSCSI disk. It is just
an ext3 partition that has a disk label. If the primary box drops, the
backup box (through the magic of clustering), knows that it
From: Kenny Lussier kluss...@gmail.com
To: gnhlug-disc...@gnhlug.org
Date: 3/18/2009 8:49 AM
Subject:Labeling Multipath drives
Hi All,
I currently have a failover cluster with a shared iSCSI disk. It is just
an ext3 partition that has a disk label. If the primary box drops
Kenny Lussier wrote:
This is true. For example, in /dev/mapper there is a device called
350002ac00092072a1. I can label the device, but that also creates
labels on what the OS sees as /dev/sdc, /dev/sdd, /dev/sde, /dev/sdf,
/dev/sdg, /dev/sdh, /dev/sdi, and /dev/sdj, so a mount fails.
This sounds similar to the problems you'd see if you did this:
mdadm --create --level=1 --raid-devices=2 /dev/md0 /dev/sda1 /dev/sdb1
mkfs.ext3 -L HiMom /dev/md0
...and you then prepared an fstab line that referenced that device by
its label, thus:
LABEL=HiMom / ext3 defaults 1 1
On Wed, Mar 18, 2009 at 9:36 AM, Kenny Lussier
This is true. For example, in /dev/mapper there is a device called
350002ac00092072a1. I can label the device, but that also creates labels on
what the OS sees as /dev/sdc, /dev/sdd, /dev/sde, /dev/sdf, /dev/sdg,
/dev/sdh, /dev/sdi, and
I wrote:
The reference to that label in the fstab confuses the kernel
because of the (apparently) duplicate labels it finds in the
mirrored partitions.
Come to think of it, I'm not sure it's kernel code that's getting
confused. Maybe it's the mount command or some library code -
whatever;
From: Kenny Lussier kluss...@gmail.com
To: mark prg...@gmail.com
CC: gnhlug-disc...@gnhlug.org
Date: 3/18/2009 9:40 AM
Subject:Re: Labeling Multipath drives
This is true. For example, in /dev/mapper there is a device called
350002ac00092072a1. I can label the device
On Wed, Mar 18, 2009 at 10:18 AM, Jeffrey O'brien
jobr...@expertserver.comwrote:
From: Kenny Lussier kluss...@gmail.com
To: mark prg...@gmail.com
CC: gnhlug-disc...@gnhlug.org
Date: 3/18/2009 9:40 AM
Subject:Re: Labeling Multipath drives
This is true. For example
On Wed, Mar 18, 2009 at 9:54 AM, Jeffrey O'brien
jobr...@expertserver.comwrote:
Kenny, you will need to install/configure the multipathing software. Linux
does have native mpath drivers which will create a virtual device from the
mutliple devices shown so /dev/mpath/mpath0p1 would consist of
12 matches
Mail list logo
