From: Steve Dickson <SteveD@redhat.com>
To: "Talpey, Thomas" <Thomas.Talpey@netapp.com>
Cc: "'nfs@lists.sourceforge.net'" <nfs@lists.sourceforge.net>
Subject: Re: [PATCH] NFS: Sign Extentions with Tru64 FSIDs.
Date: Wed, 07 Mar 2007 09:16:15 -0500 [thread overview]
Message-ID: <45EEC92F.6080302@RedHat.com> (raw)
In-Reply-To: <EXNANE01WtIIZS2TRqf00000060@exnane01.hq.netapp.com>
Talpey, Thomas wrote:
> The current code already supports disabling READDIRPLUS to
> servers that don't support it. It happens after the first bad
> response. The intentional option is a good idea for other
> reasons though, huge directories yield huge attributes.
Yes... I agree this could be useful in other applications...
>
> One problem I see with the mount option is that it might be
> silently ignored by old mount binaries. That will confuse users
> who install a new kernel and don't update util-linux/nfs-utils.
The problem is not so much old mount binaries, since they will fail
with something similar to "Unsupported nfs mount option: nordirplus",
its using new mount binaries with old kernels. The kernels
will silently ignore the option. One could tell the option is
not set by catting /proc/mounts (since the "nordirplus" would
not exist), but I agree there is potential for confusion...
But on he other hand I didn't want to increase the mount
version from 5 to 6 since I think that whole mounting version
stuff is just rats nest.. and Two, I really didn't mounts
to start failing (due to mis-versioning) for a option that
will probably never be used... But it is trivial to increase
the version, but it just causes so many headaches I was
trying to avoid it... Right or wrong that was the reasoning...
steved.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-03-07 14:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 20:35 [PATCH] NFS: Sign Extentions with Tru64 FSIDs Steve Dickson
2007-03-05 21:37 ` Trond Myklebust
2007-03-05 21:46 ` Peter Staubach
2007-03-05 22:03 ` Trond Myklebust
2007-03-05 22:22 ` Peter Staubach
2007-03-06 10:11 ` Peter Åstrand
2007-03-06 13:05 ` Trond Myklebust
2007-03-06 14:56 ` Steve Dickson
2007-03-06 21:42 ` Steve Dickson
2007-03-06 22:00 ` Talpey, Thomas
2007-03-07 14:16 ` Steve Dickson [this message]
2007-03-07 7:45 ` Peter Åstrand
2007-03-07 14:21 ` Steve Dickson
2007-03-07 14:38 ` Chuck Lever
2007-03-07 16:29 ` Peter Staubach
2007-03-08 3:08 ` Chuck Lever
2007-03-07 19:20 ` Steve Dickson
2007-03-05 21:54 ` Dan Goetzman
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=45EEC92F.6080302@RedHat.com \
--to=steved@redhat.com \
--cc=Thomas.Talpey@netapp.com \
--cc=nfs@lists.sourceforge.net \
/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.