Hi, We use EVMS on SLES9X to handle our scsi multipathing needs. We pretty much use the procedure documented in SG24-6344 Linux for zSeries: Fibre Channel Protocol Implementation Guide, page 192-234. We have 4 paths defined for each LUN. We had a failure on our SAN Volume Controller this weekend that caused EVMS to lose 2 disks (child objects). These 2 disks represent 2 of 4 paths to the same LUN. EVMS complains that the disk count in the "region" is wrong (ok, we lost 2 disks), but it won't continue without the missing disks (even though these disks were defined in EVMS as being redundant paths to the same LUN).
It seems odd that EVMS would work this way. Would anyone know how to "fool" EVMS into working with missing child objects? Shouldn't EVMS handle path failures? Novell tells me that multipathing with EVMS is not a supported configuration. I thought it was supported for non-root volumes. Sigh, Arty (35 dead penguins) ---------------------------------------------------------------------- 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
