NFS Services Administrator Guide (5900-3045, March 2013)

5 Troubleshooting NFS Services
This chapter describes tools and procedures for troubleshooting the NFS Services. This chapter
addresses the following topics:
“Common Problems with NFS” (page 93)
“Performance Tuning” (page 100)
“Logging and Tracing of NFS Services” (page 102)
Common Problems with NFS
This section lists the following common problems encountered with NFS and suggests ways to
correct them.
“Sharing a mounted filesystem as NFS filesystem through LOFS is not recommended” (page 93)
“NFS “Server Not Responding” Message” (page 94)
““Access Denied” Message” (page 95)
““Permission Denied” Message” (page 96)
““Device Busy” Message” (page 96)
““Stale File Handle” Message” (page 97)
A Program Hangs” (page 98)
“Data is Lost Between the Client and the Server” (page 98)
““Too Many Levels of Remote in Path” Message” (page 99)
Sharing a mounted filesystem as NFS filesystem through LOFS is not recommended
Problem
Sharing a mounted filesystem as NFS filesystem through LOFS creates a non-unique file handle for
the filesystem. Sharing multiple such filesystems may cause the following issues at the NFS server
and NFS client:
Incorrect file contents at the NFS server and NFS client.
Incorrect directory listing at the NFS client. The NFS client may show directories from another
LOFS filesystem.
Data corruption when writing a file, as the NFS server may write to the wrong file and
filesystem.
For these reasons, HP does not recommend sharing a mounted filesystem as NFS filesystem through
LOFS.
NOTE: A LOFS filesystem without any filesystems under it can be exported correctly as it will
have a unique file handle.
Workaround
While sharing a mounted filesystem through LOFS, manually assign a unique device-id using the
following command:
share -o fsid=device-id filesystem
Example:
#share -o fsid=222 /lo/mnt1
#share -o fsid=333 /lo/mnt2
Common Problems with NFS 93