From: Andreas Dilger <adilger@clusterfs.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: "Peter T. Breuer" <ptb@it.uc3m.es>,
Lars Marowsky-Bree <lmb@suse.de>,
linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] mount flag "direct"
Date: Tue, 3 Sep 2002 12:02:43 -0600 [thread overview]
Message-ID: <20020903180243.GR32468@clusterfs.com> (raw)
In-Reply-To: <Pine.LNX.4.44L.0209031425180.1519-100000@duckman.distro.conectiva>
On Sep 03, 2002 14:26 -0300, Rik van Riel wrote:
> On Tue, 3 Sep 2002, Peter T. Breuer wrote:
> > > Your approach is not feasible.
> >
> > But you have to be specific about why not. I've responded to the
> > particular objections so far.
>
> You make it sound like you bet your masters degree on
> doing a distributed filesystem without filesystem support ;)
Actually, we are using ext3 pretty much as-is for our backing-store
for Lustre. The same is true of InterMezzo, and NFS, for that matter.
All of them live on top of a standard "local" filesystem, which doesn't
know the things that happen above it to make it a network filesystem
(locking, etc).
That isn't to say that I agree with just taking a local filesystem and
putting it on a shared block device and expecting it to work with only
the normal filesystem code. We do all of our locking above the fs
level, but we do have some help in the VFS (intent-based lookup, patch
in the Lustre CVS repository, if people are interested).
Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/
next prev parent reply other threads:[~2002-09-03 18:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-03 15:01 [RFC] mount flag "direct" Peter T. Breuer
2002-09-03 15:13 ` Rik van Riel
2002-09-03 15:53 ` Maciej W. Rozycki
2002-09-03 16:04 ` Peter T. Breuer
2002-09-03 16:08 ` Rik van Riel
2002-09-03 15:16 ` jbradford
2002-09-03 15:37 ` Anton Altaparmakov
2002-09-03 15:44 ` Peter T. Breuer
2002-09-03 16:23 ` Lars Marowsky-Bree
2002-09-03 16:41 ` Peter T. Breuer
2002-09-03 17:07 ` David Lang
2002-09-03 17:30 ` Peter T. Breuer
2002-09-03 17:40 ` David Lang
2002-09-04 5:57 ` Helge Hafting
2002-09-04 6:21 ` Peter T. Breuer
2002-09-04 6:49 ` Helge Hafting
2002-09-04 9:15 ` Peter T. Breuer
2002-09-04 11:34 ` Helge Hafting
2002-09-03 17:26 ` Rik van Riel
2002-09-03 18:02 ` Andreas Dilger [this message]
2002-09-03 18:44 ` Daniel Phillips
2002-09-03 17:29 ` Jan Harkes
2002-09-03 18:31 ` Daniel Phillips
2002-09-03 18:20 ` Daniel Phillips
[not found] <20020907164631.GA17696@marowsky-bree.de>
2002-09-07 19:59 ` [lmb@suse.de: Re: [RFC] mount flag "direct" (fwd)] Peter T. Breuer
2002-09-07 21:14 ` [RFC] mount flag "direct" Lars Marowsky-Bree
2002-09-08 9:23 ` Peter T. Breuer
2002-09-08 9:59 ` Lars Marowsky-Bree
2002-09-08 16:46 ` 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=20020903180243.GR32468@clusterfs.com \
--to=adilger@clusterfs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lmb@suse.de \
--cc=ptb@it.uc3m.es \
--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