From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1N5mXV-0006jN-Jz for garchives@archives.gentoo.org; Wed, 04 Nov 2009 20:33:09 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 792EAE0A02; Wed, 4 Nov 2009 20:33:08 +0000 (UTC) Received: from mx3.netplus.ch (mx3.netplus.ch [213.221.143.232]) by pigeon.gentoo.org (Postfix) with ESMTP id 1F757E0A02 for ; Wed, 4 Nov 2009 20:33:08 +0000 (UTC) Received: from [81.13.241.209] (unknown [81.13.241.209]) (Authenticated sender: david.ulrich@netplus.ch) by mx3.netplus.ch (Postfix) with ESMTPSA id 738F2808C3 for ; Wed, 4 Nov 2009 21:33:07 +0100 (CET) Content-Type: text/plain; charset=iso-8859-1; format=flowed; delsp=yes Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-cluster@lists.gentoo.org Reply-to: gentoo-cluster@lists.gentoo.org Mime-Version: 1.0 (Apple Message framework v1076) Subject: Re: [gentoo-cluster] clvm/lvm2/device-mapper From: Ulrich David In-Reply-To: Date: Wed, 4 Nov 2009 21:32:49 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20091019204229.GA3602@orbis-terrarum.net> <513ABDE2-C29F-40C6-895D-11C7B39BC5BB@siesa.ch> <7D5D86B6-1465-435B-8662-2C591ADE4F3F@siesa.ch> To: gentoo-cluster@lists.gentoo.org X-Mailer: Apple Mail (2.1076) X-Archives-Salt: 3efdd597-acc8-44ff-87c2-1289c1fa2423 X-Archives-Hash: 9ccb9b70b4610132c7be81e93021a953 Le 4 nov. 2009 =E0 20:49, Robin H. Johnson a =E9crit : > 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 =20 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: > =3D=3D=3D > 254 4 12178432 dm-4 > system (254, 0) > =3D=3D=3D > > Whereas 0.4.7-r2 has: > =3D=3D=3D > 254 4 9766911 dm-4 > 254 5 2411519 dm-5 > dom0 ~ # multipath -ll > system (3600a0b80001f3e190000552a4ab06e95) > [size=3D20 GB][features=3D1 queue_if_no_path][hwhandler=3D0] > \_ round-robin 0 [prio=3D1][enabled] > \_ 0:0:1:0 sda 8:0 [active][ready] > \_ round-robin 0 [prio=3D6][active] > \_ 1:0:1:0 sdb 8:16 [active][ready] > dom0 ~ # dmsetup ls --target multipath > system (254, 0) > =3D=3D=3D I have put all results in the 2 files... I think the problem is on the =20= 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 =20 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, =20= because its my extended base partition). The only thing which is =20 changed is the addition of system4. I hope this should help. If not I could mount a disk in my blades, =20 install the system on the internal disk and try to mount a SAN volume =20= on it with the same partition scheme. So I could better test it =20 without boot problems. Regards David > --=20 > Robin Hugh Johnson > Gentoo Linux: Developer, Trustee & Infrastructure Lead > E-Mail : robbat2@gentoo.org > GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 >