Well, kinda. The only thing that can deter ReiserFS from replaying the
journal is convincing it that the physical media it's on is actually read
only. Some quick less/grep work revealed that there is no option that makes
the SCSI subsystem claim its devices are readonly (although it'd be extremely
useful for situations such as this).
It'd probably be pretty easy to make a boot disk using a hacked version of
ReiserFS that refuses to replay the journal, by adding a "return 0;" near the
top of journal_read(struct super_block *) in journal.c. However, you might
feel more comfortable sending it off for data recovery than testing kernel
hacks on it ;)
-Ryan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/