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

[dm-devel] kpartx & dm-multipath kernel module: Where/when should they be called (wrt FC4)?


I successfully managed to get multipath support on an EVA 3000
(HSV100). BTW shouldn't the policy for HSV100 be group_by_serial
(former group_by_tur)?

--- multipath.conf~        2005-04-01 22:56:49.000000000 +0200
+++ multipath.conf 2005-05-20 14:38:14.000000000 +0200
@@ -60,7 +60,7 @@
        device {
                vendor                  "HP      "
                product                 "HSV100          "
-               path_grouping_policy    multibus
+               path_grouping_policy    group_by_serial
                path_checker            tur
        device {

Anyway now I have my /dev/dm-2 block device and I had to get to the
partitions on it. After some search I found that

	   kpartx -a /dev/dm-2

did the right job and extracted "/dev/dm-2p1" onto /dev/dm-3 (is that
the indented bahaviour? Getting a new device name?).

What I wonder now, is where and how kpartx should be embedded into the
distribution's init scripts. It needs to come before any lvm parts
as this is an lvm partition.

OTOH dm-multipath needs to be modprobed even earlier and currently I'm
using a new interface in the init scripts (/etc/sysconfig/modules)
which is called after lvm setup. :(

Any chance this could still hit FC4? <8-)

Axel.Thimm at ATrpms.net

Attachment: pgpOoxQ8sCFIp.pgp
Description: PGP signature

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