I suspect that the problem has something to do with the "master" system writing something ext3 specific into the superblock while it has it mounted read-write. I can't say I'm surprised that this doesn't work. It pretty much goes against all the advice we've ever given anyone about not trying to share read-only while someone else has a file system read-write.
Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Michael MacIsaac Sent: Wednesday, June 07, 2006 3:08 PM To: [email protected] Subject: Re: Mounting ext3 disk read-only as ext2 Ronald, Thanks for the append. > Please check how the dasd driver sees the dasdd disk It sees it as "ro": # cat /proc/dasd/devices 0.0.0100(ECKD) at ( 94: 0) is dasda : active at blocksize: 4096, 546840 blocks, 2136 MB 0.0.0101(FBA ) at ( 94: 4) is dasdb : active at blocksize: 512, 524288 blocks, 256 MB 0.0.0102(ECKD) at ( 94: 8) is dasdc : active at blocksize: 4096, 54000 blocks, 210 MB 0.0.0202(ECKD) at ( 94: 12) is dasdd (ro): active at blocksize: 4096, 300420 blocks, 1173 MB 0.0.0302(ECKD) at ( 94: 16) is dasde (ro): active at blocksize: 4096, 300420 blocks, 1173 MB "Mike MacIsaac" <[EMAIL PROTECTED]> (845) 433-7061 ---------------------------------------------------------------------- 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
