From: Mike Waychison <Michael.Waychison@Sun.COM>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: John S J Anderson <jacobs@genehack.org>,
linux-kernel@vger.kernel.org,
viro@parcelfarce.linux.theplanet.co.uk,
Herbert Poetzl <herbert@13thfloor.at>
Subject: Re: bug with multiple mounts of filesystems in 2.6
Date: Mon, 26 Jul 2004 17:33:07 -0400 [thread overview]
Message-ID: <41057893.1030006@sun.com> (raw)
In-Reply-To: <1090870651.6809.62.camel@lade.trondhjem.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Trond Myklebust wrote:
> På må , 26/07/2004 klokka 12:29, skreiv John S J Anderson:
>
>> Hi --
>>
>> We're working on migrating to the 2.6 kernel series, and one big
>> problem has popped up: we have a number of NFS mounts that are
>> mounted read-only in one location and read-write in a distinct
>> location (on the same machine). With 2.4 series kernels, this worked
>> without issue, but with 2.6, it doesn't: it's not possible to mount
>> the same filesystem twice with different options for each mount; the
>> two mount points have to share the same mount options.
>
>
> That behaviour is no longer supported as it meant that you would have
> different superblocks (and hence different out-of-sync caches) between
> the 2 mountpoint. It is in any case not a behaviour that is supported on
> any other Linux filesystems.
>
How is this any different than having two seperate nfs clients accessing
the same nfs export?
> If you want readonly to be an exception, then you will have to move the
> MS_RDONLY flag from being a superblock option to being a vfsmount
> option, then propagate that vfsmount information down to all the tests
> of IS_RDONLY(inode). Not a trivial task, and not one that looms high on
> my list of priorities...
>
What ever happened to the bind ro patches that were floating around a
couple months ago?
(http://marc.theaimsgroup.com/?t=107932320200005&r=1&w=2)
What is left in getting this done? Just the touch_file bit Viro
commented on?
- --
Mike Waychison
Sun Microsystems, Inc.
1 (650) 352-5299 voice
1 (416) 202-8336 voice
http://www.sun.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTICE: The opinions expressed in this email are held by me,
and may not represent the views of Sun Microsystems, Inc.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD4DBQFBBXiTdQs4kOxk3/MRAp2CAJ9hLA43GX7breEAuFJp++noSX7hAQCYn7yw
FXXelAMC/NCetjqwC8Q67g==
=rQRx
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-07-26 21:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 16:29 bug with multiple mounts of filesystems in 2.6 John S J Anderson
2004-07-26 19:37 ` Trond Myklebust
2004-07-26 21:33 ` Mike Waychison [this message]
2004-07-26 22:30 ` Herbert Poetzl
2004-07-26 22:35 ` Trond Myklebust
2004-07-27 0:56 ` Mike Waychison
2004-07-27 2:51 ` 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=41057893.1030006@sun.com \
--to=michael.waychison@sun.com \
--cc=herbert@13thfloor.at \
--cc=jacobs@genehack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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.