Le 1 nov. 2009 à 20:54, Robin H. Johnson a écrit :

> On Sun, Nov 01, 2009 at 08:37:55PM +0100, Ulrich David wrote:
>>>> sys-fs/multipath-tools-0.4.7-r2 (0.4.8 doesn't work)
>>> Could you elaborate on how it doesn't work? What is your SAN  
>>> hardware?
>> My hardware is DS4300 turbo. I have problems running kpartx from
>> multipath-tools 0.4.8. It doesn't detect all my partitions...
>> running on "dmsetup ls --target multipath".
> If your drive is larger than 1TiB, there was a fix that got included
> with multipath-tools-0.4.8-r1, so try that first (it's pending
> stabilization).

It's only 20GB volumes.

> Or sounds like this might be bug #268961 again, that I didn't have
> enough info on before.
> - Do you see the partitions on top of the multipath device in
>  /proc/partitions?

yes I see it.
The problem is on extended partitions. I have :
sda1 -> primary (boot)
sda2 -> primary (swap)
sda3 -> primary (root)
sda4 -> extended on all the rest of disk
- sda5 -> logical partition (usr)
- sda6 -> logical partition (var)

The first 3 partitions are ok (sda1 through sda3) but It takes sda4  
instead of sda5 and sda6 .... so It doesn't recognize sda5 and sda6.

> - Can you provide a udev info dump for your multipath device?

With multipath 0.4.7-r2 (working correctly) :

dom0 ~ # multipath -ll
system (3600a0b80001f3e190000552a4ab06e95) dm-2 IBM     ,1722-600
[size=20G][features=1 queue_if_no_path][hwhandler=0]
\_ round-robin 0 [prio=0][enabled]
  \_ 0:0:1:0 sdd 8:48  [active][ready]
\_ round-robin 0 [prio=3][active]
  \_ 1:0:1:0 sdh 8:112 [active][ready]
...

dom0 ~ # dmsetup ls --target multipath
system	(254, 2)
data0r1	(254, 4)
sys1domU	(254, 3)
data0r0	(254, 1)
mpath4	(254, 0)

dom0 ~ # udevadm info --query=all  --path=/sys/block/dm-2
P: /block/dm-2
N: mapper/system
L: -100
S: block/254:2
S: dm-2
S: disk/by-id/dm-name-system
S: disk/by-id/dm-uuid-3600a0b80001f3e190000552a4ab06e95
E: UDEV_LOG=3
E: DEVPATH=/block/dm-2
E: DEVNAME=/dev/mapper/system
E: DEVTYPE=disk
E: DM_NAME=system
E: DM_MAJOR=254
E: DM_MINOR=2
E: DM_STATUS=ACTIVE
E: DM_READ_ONLY=0
E: DM_EXISTS=1
E: DM_SUSPENDED=Active
E: DM_TABLE_LIVE=1
E: DM_TABLE_INACTIVE=0
E: DM_OPEN=5
E: DM_SEGMENTS=1
E: DM_EVENTS=1
E: DM_UUID=3600a0b80001f3e190000552a4ab06e95
E: DM_TARGET_TYPES=multipath
E: DEVLINKS=/dev/block/254:2 /dev/dm-2 /dev/disk/by-id/dm-name-system / 
dev/disk/by-id/dm-uuid-3600a0b80001f3e190000552a4ab06e95


dom0 ~ # udevadm info --query=all  --path=/sys/block/sda
P: /block/sda
N: sda
S: block/8:0
S: disk/by-id/scsi-3600a0b80001f3e49000055614ac5d165
E: UDEV_LOG=3
E: DEVPATH=/block/sda
E: DEVNAME=/dev/sda
E: DEVTYPE=disk
E: ID_VENDOR=IBM
E: ID_VENDOR_ENC=IBM\x20\x20\x20\x20\x20
E: ID_MODEL=1722-600
E: ID_MODEL_ENC=1722-600\x20\x20\x20\x20\x20\x20\x20\x20
E: ID_REVISION=0914
E: ID_TYPE=disk
E: ID_SERIAL=3600a0b80001f3e49000055614ac5d165
E: ID_SERIAL_SHORT=600a0b80001f3e49000055614ac5d165
E: ID_BUS=scsi
E: DEVLINKS=/dev/block/8:0 /dev/disk/by-id/ 
scsi-3600a0b80001f3e49000055614ac5d165


David

>
>>> Upstream LVM2 merged device-mapper into LVM2, that's why the dep  
>>> has a
>>> || block.
>> So, if I install lvm2 I do not need device-mapper package to be
>> installed in order to use multipath-tools, right?
> Correct.
> LVM2 2.02.45 and newer provide device-mapper.
>
> -- 
> Robin Hugh Johnson
> Gentoo Linux: Developer, Trustee & Infrastructure Lead
> E-Mail     : robbat2@g.o
> GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85