In the end, I ended up formatting a new partition as ext2, not ReiserFS. If I also had problem with setting up /proc/dasd/devices correctly, they were minor compared to trying to use a journalling file system in R/O mode, as far as I can tell.
Live and learn, and sometimes get an interesting limp....
Nick
Nick Laflamme wrote:
Mount just gives "wrong fs type, bad option, bad superblock in /dev/dasdd1, or too many mounted file systems."
There's a flock of error messages on the virtual machine console (and in dmesg). Last and most relevant are probably:
>reiserfs: journal-837: IO error during journal replay >Replay Failure, unable to mount >sh-2022: reiserfs_read_super: unable to initialize journal space
Although looking at the dmesg log makes me wonder if I got the "(ro)" attribute correct when I was setting up /proc/dasd/devices.
Time to experiment more, I guess, if only to know how many times I shot myself in that particular foot.
Nick
Post, Mark K wrote:
Hmm. Never tried that before. There might be a conflict, since reiserfs is a _journaling_ file system (kind of pointless for a read-only file system). What are the errors you get? Does anything show up in "dmesg?"
Mark Post
-----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Nick Laflamme Sent: Tuesday, March 23, 2004 11:43 AM To: [EMAIL PROTECTED] Subject: ReiserFS in R/O mode?
Is there an inherent conflict between ReiserFS and "mount -r"?
Thanks, Nick
---------------------------------------------------------------------- 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
