mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: John S J Anderson <jacobs@genehack.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bug with multiple mounts of filesystems in 2.6
Date: Mon, 26 Jul 2004 15:37:31 -0400	[thread overview]
Message-ID: <1090870651.6809.62.camel@lade.trondhjem.org> (raw)
In-Reply-To: <86oem2hgv8.fsf@mendel.genehack.org>

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.

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...

Cheers,
  Trond

  reply	other threads:[~2004-07-26 20:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-26 16:29 John S J Anderson
2004-07-26 19:37 ` Trond Myklebust [this message]
2004-07-26 21:33   ` Mike Waychison
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=1090870651.6809.62.camel@lade.trondhjem.org \
    --to=trond.myklebust@fys.uio.no \
    --cc=jacobs@genehack.org \
    --cc=linux-kernel@vger.kernel.org \
    /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®