Hi, Craig.
I'm sorry that I missed your original post. Mike MacIsaac forwarded
some of this thread to me. (And then I signed back up to the list.
Long story!)
The usual thing that happens in Linux (and most Unix) is for the root
filesystem to be mounted read-only when /sbin/init gets control. (In
the days of INITRD, this happens AFTER the initial RAM disk has loaded
whatever modules are required and then brought the root device
online.) At that point, with your root mounted read-only, an 'fsck'
can run without damaging the filesystem. If the filesystem was
moutned R/W when 'fsck' ran, the two could easily collide, and
probably would collide, and you would have filesystem damage ranging
from minor to catastrophic.
Making the root disk read-only from the VM perspective does not change this.
Marking the root disk read-only in the boot parms does not change it
(and is recommended anyway).
Setting your root disk read-only in /etc/fstab also does not turn off
this root 'fsck' step.
If you want to coax Linux into working with read-only root, you MUST
intercept /etc/init.d/boot.roofsck (or whatever equivialent; my most
recent experience on this point centers around SLES). You will have
to either modify that script or replace it with a script of your own
design. If you like, you can swipe a copy of what I use at home:
http://www.casita.net/pub/ror/etc/init.d/boot.roroot
It expects to have a /local disk or filesystem (but is not documented).
I run with read-only root on a regular basis.
It makes the manglement of multiple systems tolerable.
-- Rick; <><
On Tue, Nov 11, 2008 at 8:08 AM, Craig Loubser
<[EMAIL PROTECTED]> wrote:
>> 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.
> Well I guess I can rule out the "fsck" then. Why the difference between
> SLES9 and SLES10 though?
>
>> Is this an ext3 file system (or reiserfs), and are you mounting it as
> ext3 instead of ext2?
>
> Is is an ext2 file system.
>
> Thanks.
>
> Regards,
> 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
>
----------------------------------------------------------------------
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
