From: "Hua Zhong" <hzhong@gmail.com>
To: "'Trond Myklebust'" <trond.myklebust@fys.uio.no>,
"'Linus Torvalds'" <torvalds@linux-foundation.org>
Cc: "'Frank van Maarseveen'" <frankvm@frankvm.com>,
"'Linux Kernel Mailing List'" <linux-kernel@vger.kernel.org>,
<akpm@linux-foundation.org>
Subject: RE: recent nfs change causes autofs regression
Date: Thu, 30 Aug 2007 22:24:56 -0700 [thread overview]
Message-ID: <002201c7eb8f$463704d0$d2a50e70$@com> (raw)
In-Reply-To: <1188536658.6626.98.camel@heimdal.trondhjem.org>
Trond,
> So you are saying that it is acceptable for the kernel to decide
> unilaterally to override mount options? Why aren't we doing that for
> any other filesystem than NFS?
I think there are two reasons.
First, I have no problem with the new behavior if it didn't cause a
regression. I am not sure about the history of other filesystems, but NFS
has had the old behavior for ages, and people get used to it.
Second, NFS is actually special as this particular setup is very common and
you'll get into this situation far too easily, as from the server you could
export two directories within a filesystem as if they were two filesystems.
Very few people actually want to mount the same local filesystem multiple
times, but under NFS this is the norm.
Last but not the least, NFS is often controlled by central corporate
policies (autofs/nis), and has to work with various clients. For example,
it's not possible to add "nosharecache" to auto.auto as almost nobody
understands it, unless you upgrade all the clients.
> Trond
next prev parent reply other threads:[~2007-08-31 5:25 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 21:07 recent nfs change causes autofs regression Hua Zhong
2007-08-30 22:37 ` Trond Myklebust
2007-08-30 22:47 ` Hua Zhong
2007-08-30 23:22 ` Trond Myklebust
2007-08-30 23:30 ` Hua Zhong
2007-08-30 23:37 ` Trond Myklebust
2007-08-30 23:44 ` Hua Zhong
2007-08-31 4:31 ` Trond Myklebust
2007-08-31 4:38 ` Linus Torvalds
2007-08-31 4:47 ` Hua Zhong
2007-08-31 4:57 ` Trond Myklebust
2007-08-31 5:09 ` Ian Kent
2007-08-31 7:50 ` Matthias Schniedermeyer
2007-08-31 1:24 ` Andrew Morton
2007-08-31 4:33 ` Trond Myklebust
2007-08-31 3:49 ` Linus Torvalds
2007-08-31 3:57 ` Hua Zhong
2007-08-31 4:44 ` Trond Myklebust
2007-08-31 4:59 ` Linus Torvalds
2007-08-31 5:04 ` Trond Myklebust
2007-08-31 5:16 ` Linus Torvalds
2007-08-31 7:40 ` Jakob Oestergaard
2007-08-31 8:07 ` Linus Torvalds
2007-08-31 8:51 ` Jakob Oestergaard
2007-08-31 16:43 ` Linus Torvalds
2007-09-03 13:20 ` Jakob Oestergaard
2007-09-03 13:43 ` Martin Knoblauch
2007-08-31 12:11 ` Trond Myklebust
2007-08-31 13:12 ` Frank van Maarseveen
2007-08-31 13:50 ` Trond Myklebust
2007-08-31 14:42 ` Frank van Maarseveen
2007-09-04 7:51 ` David Howells
2007-08-31 8:28 ` Frank van Maarseveen
2007-08-31 5:24 ` Hua Zhong [this message]
2007-08-31 5:38 ` Ian Kent
2007-08-31 8:54 ` Martin Knoblauch
2007-08-31 16:21 ` Trond Myklebust
2007-08-31 17:01 ` Linus Torvalds
2007-08-31 19:03 ` Trond Myklebust
2007-09-04 8:02 ` David Howells
2007-09-04 8:35 ` David Howells
2007-09-04 9:04 ` Linus Torvalds
2007-08-31 18:47 ` Hua Zhong
2007-08-31 19:13 ` Trond Myklebust
2007-08-31 19:35 ` Hua Zhong
2007-08-31 19:41 ` Hua Zhong
2007-09-02 0:58 ` Bill Davidsen
2007-09-04 7:54 ` David Howells
2007-09-05 12:35 ` Bill Davidsen
2007-09-05 15:34 ` David Howells
2007-09-05 12:44 ` Ian Kent
2007-09-05 15:37 ` David Howells
2007-09-05 15:50 ` Trond Myklebust
2007-09-06 5:23 ` Ian Kent
2007-09-05 16:26 ` Trond Myklebust
2007-08-31 8:14 ` Frank van Maarseveen
2007-08-31 9:05 ` Ian Kent
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='002201c7eb8f$463704d0$d2a50e70$@com' \
--to=hzhong@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=frankvm@frankvm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox