From: Gordon Lack <gmlack@freenet.co.uk>
To: linux-kernel@vger.kernel.org
Subject: NFSv3 pathname problems in 2.4 kernels
Date: Sun, 22 Jul 2001 21:08:18 +0100 [thread overview]
Message-ID: <3B5B32B2.B96E6BD3@freenet.co.uk> (raw)
I am seeing a problem at the client side when trying to obtain pathnames of NFS-mounted entries. This occurs when the NFS servers involved are Linux2.4 kernels and the clients are SGI Irix 6.5 or Solaris 2.6 (Linux 2.4 clients are Ok - 2.2 ones won't be using NFSv3).
As an example of what happens.
o The server side has a pathname of /raid/sources/prog1 - a directory.
o /raid is exported
o The client NFS mounts /raid/sources as /projects/sources
o I cd to /projects/sources/prog1 and type /bin/pwd
I expect to get /projects/sources/prog1 as the result, but I actually get /sources/prog1.
Similar mounts from Linux2.2. systems (presumably running NFSv2) produce the expected (correct) result.
I've snoop'ed the network traffic and one thing I can see is that the filehandle used in the NFSv3 mount is reported as being a different length (shorter) than those for v2.
So,
a) has anyone else encountered these problems?
b) if so, do they have a solution?
c) how is the filehandle calculated in the 2.4 kernel for NFSv3? Which routine is it in? Perhaps I could try (optionally) forcing it to be the same length as a v2 filehandle to see whether that fixes things. (I'd rather that the 2.4 kernel were optimally compatible rather than paranoically
correct.
Hoping someone can help...
next reply other threads:[~2001-07-22 23:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-22 20:08 Gordon Lack [this message]
2001-07-23 2:20 ` NFSv3 pathname problems in 2.4 kernels Neil Brown
2001-07-23 22:20 ` Gordon Lack
2001-07-23 23:38 ` Neil Brown
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=3B5B32B2.B96E6BD3@freenet.co.uk \
--to=gmlack@freenet.co.uk \
--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