Messages in this thread |  | | Date | Tue, 4 Sep 2001 17:03:22 +0000 | From | Pavel Machek <> | Subject | Re: [RFD] readonly/read-write semantics |
| |
Hi!
> > > Read-only is more complex - in addition to mount side ("does anyone want > > > it to be r/w") there is a filesystem side ("does fs agree to be r/w")... > > > > How about, say, a reiserfs mounted r/o on a shared partition (loopback > > over nfs) ? If it contains errors, maybe 2 "clients" will attempt to > > rollback at the same time. Is the solution to never mount, even r/o, > > remote journalling fs ? > > ??? Rollback is purely local thing, so NFS client doesn't matter at all. > And nfsd is just an application running on server, whether it's a kernel > thread or a normal process.
Notice he said *loopback* over nfs [i.e. mount /nfs/xyzzy -o loop,ro -t reiserfs]. Or think nbd.
And yes, being able to mount reiserfs without replaying log is usefull.
Pavel -- Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt, details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.
- 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/
|  |