Hi Carsten, It is SLES10 SP2 (kernel 2.6.16.60-0.21). SLES10 SP2 is definitely behaving differently to SLES9. Under SLES9, prior to passing control to /sbin/init, it would mount the root file system as R/O and this is without marking the boot device as "ro" in the kernel command line. Thanks to Mark and Florian, though, I was able to get around this. The key was to add the additional "ro" parameter to the kernel command line and also update /etc/fstab to mount the root file system as "ro" (I had forgotten to put this back in). Since we have a support contract with IBM for Linux on z, I will raise a PMR just to see what they say. Once again, thanks to everyone on this list.
Regards, Craig. -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Carsten Otte Sent: Wednesday, November 12, 2008 3:11 AM To: [email protected] Subject: Re: Implementing a Shared Root File System Am Mon, 10 Nov 2008 19:16:19 -0700 schrieb Mark Post <[EMAIL PROTECTED]>: The fsck is not what is causing the I/O errors. When you see "fsck succeeded" it's done and over with. Let me guess, though. Is this an ext3 file system (or reiserfs), and are you mounting it as ext3 instead of ext2? If so, then I suspect the system is trying to replay the journal, resulting in the I/O errors. There's no point in having a journaling file system that is only going to be mounted read-only. Use ext2 instead. Neither should the file system nor fsck be able to write to the volume in the first place, if it is marked (ro). Also, it should be mounted read-only by default even if you forget the additional ro in the kernel command line as long as the device itself is read-only - and that should be the case here, due to the dasd=100(ro) in the kernel command line. This clearly is a kernel bug, Craig should open a PMR for that. What distribution/kernel version are you running? so long, Carsten ---------------------------------------------------------------------- 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
