Ok. If I'm not mistaken, this is a regression introduced by the switch
of rc-sysinit.conf from starting on 'network-interface-up IFACE!=lo' to
'static-network-up'. Previously, we had a guarantee that scripts in
runlevel 2 would not be started until at least one non-loopback
interface is up.
I thought it was happening randomly however it does actually appear to happen
after rebooting the server. I do notice some errors on boot
relating to exportfs but I can't find them in any logs (or get a chance to
actually read what they say).
options on client in fstab are 'nfs
Well, I asked for the output of 'showmount $server' and what
/etc/exports shows (not just the options) because I suspected you are
having a name resolution problem at startup. Your responses so far
appear to confirm this possibility. How is the network configured on
this server - via
$showmount server (this does work so the server does seem to be running)
Hosts on server:
192.168.1.32
'/etc/exports' (there are a bunch of other folders shared, but they all have
the same options)
/media/drive1 client1(rw,no_subtree_check) client2(rw,no_subtree_check)
Network on the server
Thanks for the report.
When this happens, what does 'showmount $server' show? Does the error
happen only after a server reboot, or randomly at any time?
What mount options do you use on the client, and what does /etc/exports
show on the server?
** Changed in: nfs-utils (Ubuntu)
Importance:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/848823
Title:
mounting of nfs shares fails and must restart nfs-kernel-server
To manage notifications about this bug go to:
