Pedro, this would be true for RHEL 6.1 which supports HyperPAV and also provides transparent usage of PAVs. But it requires kernel 2.6.25+ while RHEL 5.6 is 2.6.17.
=================== Marian Gasparovic =================== "The mere thought hadn't even begun to speculate about the merest possibility of crossing my mind." >________________________________ >From: Pedro Principeza <[email protected]> >To: [email protected] >Sent: Wednesday, August 31, 2011 9:33 PM >Subject: Re: multipath.conf question > >Greetings! > >I might be absurdly wrong, but I guess PAV does not need dm-multipath to >work, does it? >My understanding came from the following presentation. > >http://www.vm.ibm.com/education/lvc/lvc0510c.pdf > >HTH, >Pedro Principeza > > > >From: Marian Gasparovic <[email protected]> >To: [email protected] >Date: 31/08/2011 16:20 >Subject: multipath.conf question >Sent by: Linux on 390 Port <[email protected]> > > > >Hello all, >RHEL 5.6, I have one disk with PAV aliases and five disks without aliases >in Linux > >lsdasd reports >0.0.0201 alias ECKD >0.0.0202 alias ECKD >0.0.0203 alias ECKD >0.0.0100 active dasda 94:0 ECKD 4096 10265MB 2628000 >0.0.0101 active dasdb 94:4 ECKD 4096 10265MB 2628000 >0.0.0102 active dasdc 94:8 ECKD 4096 25536MB 6537420 >0.0.0103 active dasdd 94:12 FBA 512 256MB 524288 >0.0.0104 active dasde 94:16 ECKD 4096 7042MB 1802880 >0.0.0200 active dasdag 94:128 ECKD 4096 23033MB 5896620 > >Now I want dasdag to be multipathed while dasda-dasde to be ignored by >multipath. > >So my first step was to use > >blacklist { > devnode "dasda" >} >But it blacklists also dasdag ! > >[root@hqmalnx1 ~]# multipath -d -v 2|grep dasda >[root@hqmalnx1 ~]# > >If I try >blacklist { > devnode "dasda." (see the dot at the end) >} > >It will blacklist dasdag, that is expected, but not what I want to achieve > >[root@hqmalnx1 ~]# multipath -d -v 2|grep dasda >\_ 0:0:256:0 dasda 94:0 [undef][ready] > > >So "dasda." works as expected, but "dasda" works more like "dasda*". The >only solution that worked for me was this > >blacklist { > devnode "dasda" >} > >blacklist_exceptions { > devnode "dasda." >... > >[root@hqmalnx1 ~]# multipath -d -v 2|grep dasda >\_ 0:0:512:0 dasdag 94:128 [undef][ready] >\_ 0:0:513:0 dasdah 94:132 [undef][ready] >\_ 0:0:514:0 dasdai 94:136 [undef][ready] >\_ 0:0:515:0 dasdaj 94:140 [undef][ready] > >Right now I am not sure if it will work also with dasd[a-z]. and similar. >The best solution would be if I can use just blacklist, no exceptions and >it will blacklist anything higher that dasdz. >Any ideas how to do that ? >Thank you > > > >=================== >Marian Gasparovic >=================== >"The mere thought hadn't even begun to speculate about the merest >possibility of crossing my mind." > >---------------------------------------------------------------------- >For LINUX-390 subscribe / signoff / archive access instructions, >send email to [email protected] with the message: INFO LINUX-390 or >visit >http://www.marist.edu/htbin/wlvindex?LINUX-390 >---------------------------------------------------------------------- >For more information on Linux on System z, visit >http://wiki.linuxvm.org/ > > >---------------------------------------------------------------------- >For LINUX-390 subscribe / signoff / archive access instructions, >send email to [email protected] with the message: INFO LINUX-390 or visit >http://www.marist.edu/htbin/wlvindex?LINUX-390 >---------------------------------------------------------------------- >For more information on Linux on System z, visit >http://wiki.linuxvm.org/ > > > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
