21.02.2013 Views

AIX 5L Problem Determination - IBM Redbooks

AIX 5L Problem Determination - IBM Redbooks

AIX 5L Problem Determination - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

4. Initiate an iptrace (client, server, or network), reproduce the problem, then<br />

view the ipreport output to determine where the problem is.<br />

8.4.2 NFS mount problems<br />

Mount problems fall into one of the following categories:<br />

► File system not exported, or not exported to a specific client.<br />

Correct server export list (/etc/exports)<br />

► Name resolution different from the name in the export list. Normally, it is due<br />

to one of the following causes:<br />

– The export list uses a fully qualified name but the client host name is<br />

resolved without a network domain. Fully qualified names cannot be<br />

resolved. Mount permission is denied. Usually, this happens after upgrade<br />

activity and can be fixed by exporting to both forms of the name.<br />

– The client has two adapters using two different names and the export only<br />

specifies one. This problem can be fixed by exporting both names.<br />

– The server cannot do a lookuphostbyname or lookuphostbyaddr onto the<br />

client. To check, make sure the following commands both resolve to the<br />

same system:<br />

host name<br />

host ip_addr<br />

► The file system mounted on the server after exportfs was run. In this case,<br />

the exportfs command is exporting the mount point and not the mounted file<br />

system. To correct this problem run:<br />

/usr/etc/exportfs -ua; /usr/etc/exportfs -a<br />

Then fix the /etc/filesystems file to mount the file system on boot, so it is<br />

already mounted when NFS starts from /etc/rc.nfs at system startup.<br />

► Changes in the exports list, mounts, or somewhere else unexpectedly can<br />

sometimes lead to mountd getting confused. This usually happens following<br />

mounting, exporting, or because of mount point conflicts and similar errors.<br />

To correct this condition, mountd needs to be restarted by using the following<br />

commands:<br />

# stopsrc -s rpc.mountd<br />

# startsrc -s rpc.mountd<br />

► The system date being extremely off on one or both machines is another<br />

source of mount problems. To fix this, it is necessary to set the correct date<br />

and time, then reboot the system.<br />

190 <strong>IBM</strong> ^ Certification Study Guide - <strong>AIX</strong> <strong>5L</strong> <strong>Problem</strong> <strong>Determination</strong> Tools and Techniques

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!