To prevent network break-ins, the “-nosuid” option is used in “/etc/vfstab” and the “/etc/auto*” configuration files used for NFS mounting filesystems. In “/var/adm/messages”, (the system log files), the following type of message appears frequently: “Date machinename enterprise: save,uid 0:setuid execution not allowed”
Category: Solaris NFS
Running “ls -la /” hangs, yet running “ls -la” to other root directories (i.e. ls -la /usr) does NOT hang. And the system logs ( i.e. /var/adm/messages) shows NFS related errors, even though this is NOT a true NFS client. Here are the some sample errors that...
Hosts remotely mount other hosts, often times via routers, bridges with straight NFS mounts or with automount. Sometimes, the process accessing those remote hosts just hangs forever or gets the message: NFS SERVER <servername> NOT RESPONDING ..sometimes followed by NFS SERVER <servername> OK
Solaris Troubleshooting NFS : NFS server error: /usr/lib/nfs/nfsd [###]: t_accept(file descriptor #/transport tcp) TLI error 7
On an NFS server, the following error shows up in /var/adm/messages: /usr/lib/nfs/nfsd: t_accept(file descriptor 5/transport tcp) TLI error 7
Stale file handles occur when a file or directory was held open by an NFS client, and then was either removed, renamed, or replaced. For example a file gets removed and a new file is created using the same inode, or if the file was...
NFS mounts in /etc/vfstab with the “mount at boot” field set to yes are not mounted at boot time.