[lkml]   [2001]   [Feb]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Reasons to honor readonly mount requests
Jeff writes:
> I understand that both ext3fs and
> reiserfs will try to fix corrupt filesystems (or at least filesystems
> with unprocessed log entries) in-place even if they're mounted
> read-only. Clearly, virtual replay means more work, but -- just for
> fun -- here are some cases in which it might matter:
> 1. You want the disk image untouched for forensic analysis or data
> recovery.
> 2. You don't trust the disk to do writes properly.
> 3. You don't trust the driver to do writes properly.
> 4. You want to test a newer or unstable FS implementation w/ option to
> go back to the older one.

Excluding the root fs (which probably isn't involved in these sorts of
things anyways), you can always turn off the "RECOVERY" flag on the
filesystem and mount ext3 as ext2, which will not do any recovery.

> 5. You're sharing the disk via:
> VMWare (multiple OS instances on 1 computer)
> passive backplane (multiple computers on 1 bus)
> PCI bridge (multiple computers w/ connected buses)
> SCSI/FC/FireWire (multiple computers sharing device)
> The merit of #5 is reduced but not quite obviated by the fact that
> it's generally unsafe to share a disk if even one party is writing to it.

Very true. Any changes made by the writer will not be noticed by the
reader if it has already cached those pages. Best to use a cluster
filesystem in all of these cases.

Cheers, Andreas
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?" -- Dogbert
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:52    [W:0.057 / U:0.300 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site