This looks related to: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=238983
(see error msg at end of comment 0) On Thu, 2007-06-14 at 08:56 -0400, Eric Sammons wrote: > Hi, > > I am trying to configure PAV on RHEL 4 and am running into a problem. I > have been working from the "How to Improve Performance with PAV November > 17, 2006" document. > > So it appears PAV is configured. > > i.e. > > DASD 0100 ON DASD 304F R/W 0X0100 SUBCHANNEL = 0000 > *DASD 0101 ON DASD 314F R/W 0X0101 SUBCHANNEL = 0001* > DASD 0190 3390 520RES R/O 107 CYL ON DASD 300B SUBCHANNEL = 0008 > DASD 0191 3390 VM350B R/O 470 CYL ON DASD 350B SUBCHANNEL = 000C > DASD 019D 3390 V01W01 R/O 146 CYL ON DASD 330B SUBCHANNEL = 0009 > DASD 019E 3390 V01W01 R/O 250 CYL ON DASD 330B SUBCHANNEL = 000A > DASD 0200 9336 (VDSK) R/W 524288 BLK ON DASD VDSK SUBCHANNEL = 0016 > *DASD 0201 ON DASD 31B0 R/W 0X0101 SUBCHANNEL = 0002* > DASD 0592 3390 V01W01 R/O 67 CYL ON DASD 330B SUBCHANNEL = 000B > > > # vmcp q pav 314f > Device 314F is a base Parallel Access Volume with the following aliases: > 31B0 > > However, after loading the kernel module: > dm_multipath 43792 0 > > and starting multipathd, oh and modifying the /etc/multipath.conf to > comment out the blacklist (and yes I modified the file before starting > multipathd) I still get no results when I run mulipath. > > > # multipath > # > > When I run multipath -v3 -d I get the following: > > load path identifiers cache > ux_socket_connect error > # > # all paths in cache : > # > path dasda not found in pathvec > > ===== path info dasda (mask 0x1f) ===== > path dasdb not found in pathvec > > ===== path info dasdb (mask 0x1f) ===== > path dasdc not found in pathvec > > ===== path info dasdc (mask 0x1f) ===== > path dasdd not found in pathvec > > ===== path info dasdd (mask 0x1f) ===== > md0 blacklisted > ram0 blacklisted > ram10 blacklisted > ram11 blacklisted > ram12 blacklisted > ram13 blacklisted > ram14 blacklisted > ram15 blacklisted > ram1 blacklisted > ram2 blacklisted > ram3 blacklisted > ram4 blacklisted > ram5 blacklisted > ram6 blacklisted > ram7 blacklisted > ram8 blacklisted > ram9 blacklisted > > > I am concerned about the ux_socket_connect error and the not found in > pathvec errors. Anyone know what might be going on here? Am I missing > something here? > > thanks! > Eric > > ---------------------------------------------------------------------- > 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 -- Brad Hinson <[EMAIL PROTECTED]> Technical Account Manager Red Hat, Inc. (888) 733-4281 x44198 ---------------------------------------------------------------------- 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
