Thank you, that worked. I saw that reply earlier but when I searched the logs I couldn't find it. This would also suggest that this is fixed with SP1 then.
-----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Robert J Brenneman Sent: Thursday, January 27, 2005 3:25 PM To: [email protected] Subject: Re: EVMS question for FCP device Try mounting /dev/evms/md/md0 with the barrier option turned off. for reiser like this: mount /dev/evms/md/md0 /<somewhere> -o barrier=none for ext3 like this: mount /dev/evms/md/md0 /<somewhere> -o barrier=0 Jay Brenneman Linux Test and Integration Center T/L: 295 - 7745 Extern: 845 - 435 - 7745 [EMAIL PROTECTED] "Wiggins, Mark" <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[email protected]> 27/01/2005 13:40 Please respond to Linux on 390 Port To [email protected] cc Subject EVMS question for FCP device I've been trying to get a multipath FCP device attach to my SLES9 instance on z/VM 5.1. I feel as though I've followed the directions (Redbook 6344 - Chap. 9, Multipath FCP on SuSE SLES9) but I end up getting either a "broken pipe" error when trying to mount it from EVMSGUI and I get "wrong fs type, bad option, bad superblock on /dev/evms/md/md0, or too many mounted file systems" when I try to mount it on linux. Quickly, let me go through the steps and see if anyone can see where I've went wrong. ATT A210 to LINUX1 in VM (both are defined as TYPE=FCP). ATT A310 to LINUX1 in VM >From YAST, HARDWARE, ZFCP, ADD 0.0.a210 WWPN1 LUN 502f 0.0.a310 WWPN2 LUN 502f The WWPN's are different but the LUN's are the same. These are defined correctly, because I've been able to use each path individual, just not as multipath. Then from EVMSGUI - add DOS segment manager to a210 - select freespace object and create segment for a210 - create region MD Multipath Region Manager and select a210 and a310 - I skip the RAID0 part because I've only got 1 LUN - create compatability volume - Make filesystem (ReiserFS) - Of course I've "saved" after each step as directed - chkconfig evms.boot on Actually, it will mount if I use EXT3 instead of ReiserFS, but I can only get it to mount "read-only". With ReiserFS it won't mount at all. In my searching I did notice suggestions of applying BD-Claim Patch, which sounds like it might resolve my problem. In addition to that, is this possibly fixed with SP1? I noticed a section in there stating "* Added patches for OES to EVMS.", just wondering if that would help. Mark Wiggins University of Connecticut Operating Systems Programmer 860-486-2792 ---------------------------------------------------------------------- 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 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 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
