Re: more attempts to resolve NSF issues

2011-10-24 Thread Mark Eackloff
On 10/23/2011 11:03 PM, Bill Davidsen wrote: > Mark Eackloff wrote: >> I am fishing a bit here, but I have no_root_squash as an option in my >> exports (server) file. When the client tries to mount the directory >> automatically at boot time through the entry in /etc/fstab I believe the >> request

Re: more attempts to resolve NSF issues

2011-10-23 Thread Bill Davidsen
Mark Eackloff wrote: > I am fishing a bit here, but I have no_root_squash as an option in my > exports (server) file. When the client tries to mount the directory > automatically at boot time through the entry in /etc/fstab I believe the > request is identified as coming from root. See the "User

Re: more attempts to resolve NSF issues

2011-10-23 Thread Mark Eackloff
I am fishing a bit here, but I have no_root_squash as an option in my exports (server) file. When the client tries to mount the directory automatically at boot time through the entry in /etc/fstab I believe the request is identified as coming from root. See the "User ID Mapping" section in man (5

Re: more attempts to resolve NSF issues

2011-10-23 Thread Genes MailLists
One question - is this the only export which would be available to the client in question? Is it possible there are others which for some reason may be interfering (I have seen this issue in the past with overlapping exports). -- users mailing list users@lists.fedoraproject.org To unsubscrib

more attempts to resolve NSF issues

2011-10-23 Thread Gerhard Magnus
I can ping (and ssh) the server from the client. When I restart nfs and nfslock on the server I get this in the server /var/log/messages: PuteF kernel: [25572.902466] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory PuteF kernel: [25572.902504] NFSD: starting 90-second grac