Le 4 nov. 2009 à 20:49, Robin H. Johnson a écrit :
> On Wed, Nov 04, 2009 at 04:33:23PM +0100, Ulrich David wrote:
>> Just another question with dependencies... I just update lvm2 to
>> last version but on my amd64 10.0 profile
>> "system" needs e2fsprogs and e2fsprogs-libs
>> lvm2 needs util-linux
>>
>> but util-linux is blocked by e2fsprogs....
> Upgrade your e2fsprogs+e2fsprogs-libs first.
> Portage was supposed to handle that upgrade automatically.
>
> Can we see the output of:
> # emerge -pv e2fsprogs e2fsprogs-libs util-linux lvm2
I just add ~amd64 keywords on sys-libs/e2fsprogs-libs and e2fsprogs
before upgrading and now It's okay. Thanks for the tip !
> Thanks for the cmd output, but just wondering if part of the 0.4.8 run
> was missing something, as it jumps:
> ===
> 254 4 12178432 dm-4
> system (254, 0)
> ===
>
> Whereas 0.4.7-r2 has:
> ===
> 254 4 9766911 dm-4
> 254 5 2411519 dm-5
> dom0 ~ # multipath -ll
> system (3600a0b80001f3e190000552a4ab06e95)
> [size=20 GB][features=1 queue_if_no_path][hwhandler=0]
> \_ round-robin 0 [prio=1][enabled]
> \_ 0:0:1:0 sda 8:0 [active][ready]
> \_ round-robin 0 [prio=6][active]
> \_ 1:0:1:0 sdb 8:16 [active][ready]
> dom0 ~ # dmsetup ls --target multipath
> system (254, 0)
> ===
I have put all results in the 2 files... I think the problem is on the
extended partition (partioned with fdisk) because :
with 0.4.7-r2 :
dm-0 -> mapper/system -> (sda,sdb)
dm-1 -> mapper/system1 -> (sda1,sdb1 primary partition)
dm-2 -> mapper/system2 -> (sda2,sdb2 primary partition)
dm-3 -> mapper/system3 -> (sda3,sdb3 primary partition)
dm-4 -> mapper/system5 -> (sda5,sdb5 first part of extended partition)
dm-5 -> mapper/system6 -> (sda6,sdb6 second part of extended partition)
dom0 ~ # ls -la /dev/dm-*
lrwxrwxrwx 1 root root 13 Nov 4 14:51 /dev/dm-0 -> mapper/system
lrwxrwxrwx 1 root root 14 Nov 4 14:51 /dev/dm-1 -> mapper/system1
lrwxrwxrwx 1 root root 14 Nov 4 14:51 /dev/dm-2 -> mapper/system2
lrwxrwxrwx 1 root root 14 Nov 4 14:51 /dev/dm-3 -> mapper/system3
lrwxrwxrwx 1 root root 14 Nov 4 14:51 /dev/dm-4 -> mapper/system5
lrwxrwxrwx 1 root root 14 Nov 4 14:51 /dev/dm-5 -> mapper/system6
dom0 ~ # ls -la /dev/mapper/
total 0
drwxr-xr-x 2 root root 180 Nov 4 14:51 .
drwxr-xr-x 18 root root 14260 Nov 4 13:54 ..
lrwxrwxrwx 1 root root 16 Nov 4 14:51 control -> ../device-mapper
brw-rw---- 1 root disk 254, 0 Nov 4 14:51 system
brw-rw---- 1 root disk 254, 1 Nov 4 14:51 system1
brw-rw---- 1 root disk 254, 2 Nov 4 14:51 system2
brw-rw---- 1 root disk 254, 3 Nov 4 14:51 system3
brw-rw---- 1 root disk 254, 4 Nov 4 14:51 system5
brw-rw---- 1 root disk 254, 5 Nov 4 14:51 system6
If I upgrade multipath to 0.4.8-r1 on a running system with mounted
partitions (using multipath-0.4.7-r2) :
dom0 ~ # emerge -p multipath-tools
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] sys-fs/multipath-tools-0.4.8-r1
dom0 ~ # emerge multipath-tools
...
dom0 ~ # dmsetup ls --target multipath --exec "/sbin/kpartx -l"
system1 : 0 1955839 /dev/mapper/system 1
system2 : 0 7815168 /dev/mapper/system 1955840
system3 : 0 7815168 /dev/mapper/system 9771008
system4 : 0 24356864 /dev/mapper/system 17586176
system5 : 0 19533823 /dev/dm-3 1
system6 : 0 4823039 /dev/dm-3 19533825
dom0 ~ # dmsetup ls --target multipath --exec "/sbin/kpartx -av"
add map system1 (254:1): 0 1955839 linear /dev/mapper/system 1
add map system2 (254:2): 0 7815168 linear /dev/mapper/system 1955840
add map system3 (254:3): 0 7815168 linear /dev/mapper/system 9771008
add map system4 (254:6): 0 24356864 linear /dev/mapper/system 17586176
device-mapper: reload ioctl failed: Invalid argument
add map system5 : 0 19533823 linear 254:6 17586177
device-mapper: reload ioctl failed: Invalid argument
add map system6 : 0 4823039 linear 254:6 37120001
dom0 ~ # ls -al /dev/mapper/
total 0
drwxr-xr-x 2 root root 200 Nov 4 21:23 .
drwxr-xr-x 18 root root 14280 Nov 4 21:23 ..
lrwxrwxrwx 1 root root 16 Nov 4 14:51 control -> ../device-mapper
brw-rw---- 1 root disk 254, 0 Nov 4 14:51 system
brw-rw---- 1 root disk 254, 1 Nov 4 14:51 system1
brw-rw---- 1 root disk 254, 2 Nov 4 14:51 system2
brw-rw---- 1 root disk 254, 3 Nov 4 14:51 system3
brw-rw---- 1 root disk 254, 6 Nov 4 21:23 system4
brw-rw---- 1 root disk 254, 4 Nov 4 14:51 system5
brw-rw---- 1 root disk 254, 5 Nov 4 14:51 system6
dom0 ~ # ls -al /dev/dm*
lrwxrwxrwx 1 root root 13 Nov 4 14:51 /dev/dm-0 -> mapper/system
lrwxrwxrwx 1 root root 14 Nov 4 14:51 /dev/dm-1 -> mapper/system1
lrwxrwxrwx 1 root root 14 Nov 4 14:51 /dev/dm-2 -> mapper/system2
lrwxrwxrwx 1 root root 14 Nov 4 14:51 /dev/dm-3 -> mapper/system3
lrwxrwxrwx 1 root root 14 Nov 4 14:51 /dev/dm-4 -> mapper/system5
lrwxrwxrwx 1 root root 14 Nov 4 14:51 /dev/dm-5 -> mapper/system6
lrwxrwxrwx 1 root root 14 Nov 4 21:23 /dev/dm-6 -> mapper/system4
kpartx failed on mapping system4 which should be not mapped (I think,
because its my extended base partition). The only thing which is
changed is the addition of system4.
I hope this should help. If not I could mount a disk in my blades,
install the system on the internal disk and try to mount a SAN volume
on it with the same partition scheme. So I could better test it
without boot problems.
Regards
David
> --
> 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
>
|
