All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Sven Hoexter <shoexter@gmx.de>, linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION] nfs client: Read-only file system (2.6.19-rc1,2)
Date: Wed, 18 Oct 2006 19:44:17 +0200	[thread overview]
Message-ID: <453667F1.4040504@gmail.com> (raw)
In-Reply-To: <1161192121.6095.58.camel@lade.trondhjem.org>

Trond Myklebust wrote:
> I'll bet that you have always had a subdirectory of the exact same
> filesystem mounted somewhere else ro, right?

Yup, exactly: /usr -ro and /home -rw on the same (hda3) partition.

> The new NFS mount code will put those in the same superblock, and
> whichever directory gets mounted first will determine whether or not the
> superblock is marked as read-only.
> Basically, NFS is now doing the exact same thing that local filesystems
> have been doing all the time: if it is on the same disk, then it is all
> represented by the same superblock. OTOH, if your server is exporting
> more than one partition, then different partitions will be represented
> by different superblocks.
> We need to do this for the same reason that local filesystems do it: it
> is the only way to ensure cache consistency. Otherwise, if you make
> changes to a file that happens to be mounted in more than one place,
> then you will see inconsistent results on the other mountpoints.

thanks for clarification,
-- 
http://www.fi.muni.cz/~xslaby/            Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8  22A0 32CC 55C3 39D4 7A7E

  reply	other threads:[~2006-10-18 17:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-17 15:24 [REGRESSION] nfs client: Read-only file system (2.6.19-rc1,2) Jiri Slaby
2006-10-17 16:54 ` Trond Myklebust
2006-10-18  6:27   ` Sven Hoexter
2006-10-18  8:52     ` Jiri Slaby
2006-10-18 15:46       ` Jiri Slaby
2006-10-18 17:22         ` Trond Myklebust
2006-10-18 17:44           ` Jiri Slaby [this message]
2006-10-18 18:02             ` J. Bruce Fields
2006-10-18 18:06               ` Jiri Slaby

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=453667F1.4040504@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shoexter@gmx.de \
    --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.