Hi List, I have been trying to implement a R/O root file system with SLES10 SP2 following the IBM Redpaper "Sharing and maintaining Linux under z/VM" at http://www.redbooks.ibm.com/redpieces/abstracts/redp4322.html?Open but I have found an issue with the way that SLES10 SP2 tries to fsck and mount the root file system as R/W before passing control to /sbin/init . You can see later on where boot.rootfsck, modified for the Read-Only root, gets executed, but at that point it is too late... I start getting file system errors, because the minidisk containing the root file system is defined as R/O to the Linux guest. Eventually the root file system becomes unreadable. I checked this process on a SLES9 system.... It mounts the root file system as R/O just before passing control to /sbin/init. I am wondering if this is an intentional change in SLES10 or this is a "bug".
Here is an extract of the log from a SLES10 SP2 system during boot processing: Waiting for device /dev/dasda1 to appear: ok rootfs: major=94 minor=1 devn=24065 fsck 1.38 (30-Jun-2005) Ý/bin/fsck.ext2 (1) -- /¨ fsck.ext2 -a /dev/dasda1 /dev/dasda1: clean, 51899/874368 files, 299859/1748676 blocks fsck succeeded. Mounting root device read-write. Mounting root /dev/dasda1 end_request: I/O error, dev dasda, sector 192 Buffer I/O error on device dasda1, logical block 0 lost page write due to I/O error on dasda1 end_request: I/O error, dev dasda, sector 13107640 Buffer I/O error on device dasda1, logical block 1638431 lost page write due to I/O error on dasda1 mount: you must specify the filesystem type INIT: version 2.86 booting System Boot Control: Running /etc/init.d/boot Mounting procfs at /proc..done Mounting sysfs at /sys..done Mounting debugfs at /sys/kernel/debug..done Initializing /dev..done Mounting devpts at /dev/pts..done Boot logging started on /dev/ttyS0(/dev/console (deleted)) at Fri Oct 24 18:13:38 2008 Adding 215896k swap on /dev/disk/by-path/ccw-0.0.0102-part1. Priority:-1 extents:1 across:215896k kjournald starting. Commit interval 5 seconds EXT3 FS on dasde1, internal journal EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. ##### EXECUTING boot.rootfsck Read-only root: In modified /etc/init.d/boot.rootfsck For comparison, here is a SLES9 log: Waiting for device /dev/dasda1 to appear: ok rootfs: major=94 minor=1 devn=24065 rootfs: /sys/block/dasda/dasda1 major=94 minor=1 devn=24065 kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. Trying to move old root to /initrd ... /initrd does not exist. Ignored. Unmounting old root Trying to free ramdisk memory ... failed Freeing unused kernel memory: 116k freed INIT: version 2.85 booting System Boot Control: Running /etc/init.d/boot Mounting /proc filesystem..done Mounting sysfs on /sys..done Mounting /dev/pts..done Boot logging started on /dev/ttyS0(/dev/console) at Fri Oct 24 18:19:21 2008 Mounting shared memory FS on /dev/shm..done Activating swap-devices in /etc/fstab... Adding 129972k swap on /dev/dasdb1. Priority:-1 extents:1 Adding 215896k swap on /dev/dasdc1. Priority:-2 extents:1 Ý1A..doneChecking root file system... Thanks in advance, Craig. ---------------------------------------------------------------------- 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
