From: "Peter T. Breuer" <ptb@it.uc3m.es>
To: riel@conectiva.com.br
Cc: linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] mount flag "direct" (fwd)
Date: Tue, 3 Sep 2002 17:39:31 +0200 (MET DST) [thread overview]
Message-ID: <200209031539.g83FdVb02733@oboe.it.uc3m.es> (raw)
Hi!
Thanks for the comment!
On Tue, 3 Sep 2002, Peter T. Breuer wrote:
> > Rationale:
> > No caching means that each kernel doesn't go off with its own idea of
> > what is on the disk in a file, at least. Dunno about directories and
> > metadata.
> And what if they both allocate the same disk block to another
> file, simultaneously ?
I see - yes, that's a good one.
I assumed that I would need to make several VFS operations atomic
or revertable, or simply forbid things like new file allocations or
extensions (i.e. the above), depending on what is possible or not.
This is precisely the kind of objection that I want to hear about.
OK - reply:
It appears that in order to allocate away free space, one must first
"grab" that free space using a shared lock. That's perfectly feasible.
Thank you.
Where could I intercept the block allocation in VFS?
> A mount option isn't enough to achieve your goal.
>
> It looks like you want GFS or OCFS. Info about GFS can be found at:
No, I don't want ANY FS. Thanks, I know about these, but they're not
it. I want support for /any/ FS at all at the VFS level.
> http://www.opengfs.org/
> http://www.sistina.com/ (commercial GFS)
> Dunno where Oracle's cluster fs is documented.
I know about that too, but no, I do not want ANY FS, I want /any/ FS.
:-)
Peter
next reply other threads:[~2002-09-03 15:35 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-03 15:39 Peter T. Breuer [this message]
2002-09-03 15:44 ` Rik van Riel
2002-09-03 15:50 ` Peter T. Breuer
2002-09-03 15:56 ` Chris Wedgwood
2002-09-03 15:59 ` Peter T. Breuer
2002-09-03 16:09 ` Richard B. Johnson
2002-09-03 16:29 ` Peter T. Breuer
2002-09-03 16:33 ` Rik van Riel
2002-09-03 17:32 ` Richard B. Johnson
2002-09-03 18:53 ` Lars Marowsky-Bree
2002-09-03 21:07 ` Peter T. Breuer
2002-09-03 21:15 ` Andreas Dilger
2002-09-03 21:15 ` Rik van Riel
2002-09-03 21:54 ` Anton Altaparmakov
2002-09-03 22:46 ` Andreas Dilger
2002-09-03 23:19 ` Daniel Phillips
2002-09-04 0:18 ` Anton Altaparmakov
2002-09-04 5:23 ` David Lang
2002-09-04 7:16 ` Helge Hafting
2002-09-04 8:39 ` Andreas Dilger
2002-09-04 12:07 ` Helge Hafting
2002-09-04 13:03 ` Hans Reiser
2002-09-04 8:41 ` Peter T. Breuer
2002-09-04 7:50 ` Joachim Breuer
[not found] ` <3D75F8B0.8C7E974E@aitel.hist.no>
2002-09-04 21:26 ` Joachim Breuer
2002-09-04 9:26 ` Lars Marowsky-Bree
2002-09-03 16:58 ` Anton Altaparmakov
2002-09-03 17:26 ` Peter T. Breuer
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=200209031539.g83FdVb02733@oboe.it.uc3m.es \
--to=ptb@it.uc3m.es \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®