lkml.org 
[lkml]   [2001]   [Sep]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFD] readonly/read-write semantics
Hi!

> > 2) I'd like to see a readonly mount state defined as "the filesystem will
> > not change. Period." Not for system calls in progress, not for cache
> > synchronization, not to set an "unmounted" flag, not for writes that are
> > queued in the device driver or device. (That last one may stretch
> > feasability, but it's a worthy goal anyway).
>
> It doesn't work. Think of r/o mounting of remote filesystem. Do you
> suggest that it should make it impossible to change from other clients?

Okay, make the definition

"this kernel will not attempt to change anything on that filesystem".

This does not neccesarily mean -oro should have this semantics, maybe we
need something like -orealro, but we should have some mode when writing on
that disk is taboo. [I need that for suspend-to-disk support: I need to
write suspend data do disk, while I need noone to touch those disks,
because I already took snapshot.]
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/

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