You could try mounting it with the "noload" option. Might work...never tried it.
Leland On 6/6/06 12:39 PM, "Michael MacIsaac" <[EMAIL PROTECTED]> wrote: > Hello list, > > I'm trying to mount an ext3 file system as ext2, I thought this could > *always* be done, but I'm finding otherwise. > > I write to a disk on a "master" Linux and then want to link it read-only > on "clones". I use a LINK statement in the USER DIRECTory, use "(ro)" in > zipl.conf and "ro" in fstab. > > If I mount the read-only disk as ext3 on the clones, it mounts, but there > are errors on the console (I assume) because the file system is trying to > write to the journal. Wehn I changed "ext3" to "ext2" in fstab on the > clones I found that the file system would no longer mount. On the > interactive mount command I get the error: > mount: wrong fs type, bad option, bad superblock on /dev/dasdd1, > or too many mounted file systems > > On the console I see the error: > Jun 6 13:35:11 lat132 kernel: EXT2-fs: dasdd1: couldn't mount because > of unsupp > orted optional features (4000000). > > However, if I shut down the master, the clones can mount as ext2 with no > problem. Here is a summary: > R/W on master R/O on clones > Mount as ext3 yes yes > Mount as ext2 w/master shutdown N/A yes > Mount as ext2 w/master running yes NO > > Is this behavior expected? > Thanks. > > > "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 > ---------------------------------------------------------------------- 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
