On Thu, 2005-11-24 at 22:43 +0100, Eric TANGUY wrote: > I have a fc3 server and fc4 clients. Each client mount 2 nfs directory > at bootup : > 192.168.10.10:/home /home nfs exec,dev,suid,rw 1 1 > 192.168.10.10:/usr/local /usr/local nfs exec,dev,suid,ro 1 1 > > Since today /home is not mounted at boot (but /usr/local is mounted) > but this seems to be randomly. Seems some unusual options. If I were doing the same thing, mine would be something like: 192.168.10.10:/home /home nfs auto,noexec,nodev,intr,udp 192.168.10.10:/usr/local /usr/local nfs auto,nodev,intr,udp,ro Although the "defaults" set "auto" and "rw", and other things, I like to see what options I've set. I have to read the man files to find out what the defaults are. The "exec" and "dev" options would be unusual for home space, if not actually risky, I can't see why you'd want dev for /usr/local, either. And the "1 1" checking options don't seem sensible across a network, let the machine with the drive do that. Perhaps they're something to do with the problems you're having (it not being able to fsck something on a remote system).

Le mardi 29 novembre 2005 à 12:40 +0100, Eric TANGUY a écrit : > > On Thu, 2005-11-24 at 22:43 +0100, Eric TANGUY wrote: > >> I have a fc3 server and fc4 clients. Each client mount 2 nfs directory > >> at bootup : > >> 192.168.10.10:/home /home nfs exec,dev,suid,rw 1 1 > >> 192.168.10.10:/usr/local /usr/local nfs exec,dev,suid,ro 1 1 > >> > >> Since today /home is not mounted at boot (but /usr/local is mounted) > >> but this seems to be randomly. > > > > Seems some unusual options. If I were doing the same thing, mine would > > be something like: > > > > 192.168.10.10:/home /home nfs auto,noexec,nodev,intr,udp > > 192.168.10.10:/usr/local /usr/local nfs auto,nodev,intr,udp,ro > > > > Although the "defaults" set "auto" and "rw", and other things, I like to > > see what options I've set. I have to read the man files to find out > > what the defaults are. > > > > The "exec" and "dev" options would be unusual for home space, if not > > actually risky, I can't see why you'd want dev for /usr/local, either. > > > > And the "1 1" checking options don't seem sensible across a network, let > > the machine with the drive do that. Perhaps they're something to do > > with the problems you're having (it not being able to fsck something on > > a remote system). > > > So i put the values you give but it seems to solve nothing : > sometimes, at bootup /usr/local is mounted and not /home the only messages > related to this in /var/log/messages is : > Nov 29 12:32:26 s237-1 rpc.idmapd: nfsdreopen: Opening '' failed: errno 2 > (No such file or directory) > Which indicates nothing to me. > > I see also some errors at the shutdown : > Nov 29 08:31:22 s237-1 rpc.mountd: Caught signal 15, un-registering and > exiting. > Nov 29 08:31:26 s237-1 kernel: nfsd: last server has exited > Nov 29 08:31:26 s237-1 kernel: nfsd: unexporting all filesystems > Nov 29 08:31:27 s237-1 ntpd[2439]: ntpd exiting on signal 15 > Nov 29 08:31:27 s237-1 kernel: Badness in interruptible_sleep_on_timeout > at kernel/sched.c:3403 (Not tainted) > Nov 29 08:31:27 s237-1 kernel: [<c031d2b2>] > interruptible_sleep_on_timeout+0xf7/0x114 > Nov 29 08:31:27 s237-1 kernel: [<c012b213>] group_send_sig_info+0x59/0x63 > Nov 29 08:31:27 s237-1 kernel: [<c011c4de>] default_wake_function+0x0/0xc > Nov 29 08:31:27 s237-1 kernel: [<e02814fb>] lockd_down+0xbe/0x120 [lockd] > Nov 29 08:31:27 s237-1 kernel: [<e03f5cf7>] nfs_kill_super+0x5c/0x5e [nfs] > Nov 29 08:31:27 s237-1 kernel: [<c01699ed>] deactivate_super+0x60/0x71 > Nov 29 08:31:27 s237-1 kernel: [<c017eb4e>] sys_umount+0x33/0x73 > Nov 29 08:31:27 s237-1 kernel: [<c0179b9a>] dput+0x115/0x26d > Nov 29 08:31:27 s237-1 kernel: [<c0164719>] __fput+0x13d/0x18f > Nov 29 08:31:27 s237-1 kernel: [<c0162ed2>] filp_close+0x3e/0x62 > Nov 29 08:31:27 s237-1 kernel: [<c0103985>] sysenter_past_esp+0x56/0x79 > Nov 29 08:31:29 s237-1 rpc.statd[2110]: Caught signal 15, un-registering > and exiting. > > But i can't see where the problem come from. > Thanks > Eric > No one could help me with this problem or help me to increase the error messages putting something in debug mode ? Thanks Eric