Hi All I am writing a NFSv3 server as part of the Gluster clustered FS. To start with, I've implemented the Mountv3 protocol and am just starting out with NFSv3. In NFSv3, the first thing I've implemented is the FSINFO and GETATTR calls to support mounting with NFS client. The problem I am facing is this. The Linux NFS client fails to mount the remote export even though it is successfully receiving the file handle from the MNT request and the result of the FSINFO call. This is shown in the attached pcap file, which would be best viewed through wireshark with "rpc" as the display filter. The command line output is shown below: root@indus:statcache# mount 127.0.0.1:/pos1 /mnt -o noacl,nolock mount.nfs: mounting 127.0.0.1:/pos1 failed, reason given by server: No such file or directory This happens even though, we're told the following by showmount. root@indus:statcache# showmount -e Export list for indus: /pos1 (everyone) /pos2 (everyone) /pos3 (everyone) /pos4 (everyone) root@indus:statcache# ..where /pos1, /pos2, etc are exports from the locally running Gluster NFS server. As you'll notice in the trace, there is no NFSv3 request after the FSINFO, so I've a feeling it could be that some field in the FSINFO reply is not what the Linux NFS client is expecting. Could that be the reason for the mount failure? What else should I be looking into to investigate this further? The client is a 2.6.18-5 kernel supplied with Debian on an AMD64 box. nfs-utils is version 1.1.4. Many thanks, -Shehjar
Attachment:
mount.dump
Description: Binary data
