From: Olaf Kirch <okir@suse.de>
To: trond.myklebust@fys.uio.no
Cc: Charles Lever <Charles.Lever@netapp.com>, nfs@lists.sourceforge.net
Subject: Re: NFS suport block sharing
Date: Thu, 19 Feb 2004 10:05:51 +0100 [thread overview]
Message-ID: <20040219090551.GA19999@suse.de> (raw)
In-Reply-To: <36604.207.214.87.84.1077165546.squirrel@webmail.uio.no>
On Thu, Feb 19, 2004 at 05:39:06AM +0100, Trond Myklebust wrote:
> Sure it is. Just add the equivalent of Olaf's patch for the
> forcedirectio flag into the external patch that adds forcedirectio
> support. "forcedirectio" does indeed not care about inode aliasing, but it
> is the *only* such case.
But it is non-intuitive. You mount something with one set of flags,
but get a totally different behavior. That is arguably a bug.
I concede that we're arguing a very rarely used setup here, so I'm not
going to be religious about it :-)
Let me state my point though: how many people actually do mount a file
system twice? And if they do, wouldn't that be exactly _because_ they
want different semantics on the two mounts?
In general I think sharing the super block itself is not a good idea,
even for block file systems, because flags such as ro and sync get
ignored as well. These flags, as well as the RPC transport stuff,
might be better placed in the vfsmount as they're really per-mount,
not per-filesystem.
Olaf
--
Olaf Kirch | Stop wasting entropy - start using predictable
okir@suse.de | tempfile names today!
---------------+
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-02-19 9:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 2:27 NFS suport block sharing Lever, Charles
2004-02-19 4:39 ` trond.myklebust
2004-02-19 9:05 ` Olaf Kirch [this message]
2004-02-19 16:37 ` trond.myklebust
-- strict thread matches above, loose matches on Subject: below --
2004-02-20 13:25 barrie_spence
2004-02-19 14:51 Lever, Charles
2004-02-18 20:17 Lever, Charles
2004-02-18 16:37 Olaf Kirch
2004-02-19 0:04 ` trond.myklebust
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=20040219090551.GA19999@suse.de \
--to=okir@suse.de \
--cc=Charles.Lever@netapp.com \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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.