From: Xavier Bestel <xavier.bestel@free.fr>
To: Alexander Viro <viro@math.psu.edu>
Cc: Jean-Marc Saffroy <saffroy@ri.silicomp.fr>,
Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>,
Bryan Henderson <hbryan@us.ibm.com>,
linux-fsdevel@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [RFD] readonly/read-write semantics
Date: 04 Sep 2001 12:20:28 +0200 [thread overview]
Message-ID: <999598828.11178.8.camel@nomade> (raw)
In-Reply-To: <Pine.GSO.4.21.0109040612300.26423-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0109040612300.26423-100000@weyl.math.psu.edu>
On mar, 2001-09-04 at 12:15, Alexander Viro wrote:
>
>
> On 4 Sep 2001, Xavier Bestel wrote:
>
> > On mar, 2001-09-04 at 06:09, Alexander Viro wrote:
> >
> > > 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.
Sorry, I meant journal replaying ... AFAIK, this operation will write on
the media even if mounted r/o.
Xav
next prev parent reply other threads:[~2001-09-04 10:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-31 23:35 [RFD] readonly/read-write semantics Bryan Henderson
2001-09-01 4:23 ` Alexander Viro
2001-09-01 14:42 ` Ingo Oeser
2001-09-01 16:44 ` Alexander Viro
2001-09-01 17:13 ` Nicholas Knight
2001-09-04 2:07 ` Jean-Marc Saffroy
2001-09-04 4:09 ` Alexander Viro
2001-09-04 9:26 ` Xavier Bestel
2001-09-04 10:15 ` Alexander Viro
2001-09-04 10:20 ` Xavier Bestel [this message]
2001-09-04 10:28 ` Alexander Viro
2001-09-04 10:59 ` Xavier Bestel
2001-09-04 11:29 ` Alexander Viro
2001-09-04 17:03 ` Pavel Machek
2001-09-04 16:58 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2001-09-05 2:34 Bryan Henderson
2001-09-04 19:50 Bryan Henderson
2001-09-05 2:15 ` Alexander Viro
2001-09-04 18:39 Bryan Henderson
2001-09-01 0:38 Bryan Henderson
2001-08-31 17:18 [Q] [VFS] NULL f_dentry for opened files ; possible race condition Jean-Marc Saffroy
2001-08-31 20:56 ` [RFD] readonly/read-write semantics Alexander Viro
2001-09-01 13:08 ` Juan Quintela
2001-09-04 1:16 ` Jean-Marc Saffroy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=999598828.11178.8.camel@nomade \
--to=xavier.bestel@free.fr \
--cc=hbryan@us.ibm.com \
--cc=ingo.oeser@informatik.tu-chemnitz.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=saffroy@ri.silicomp.fr \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.