Red Hat Bugzilla – Bug 493039
Start-up ordering causes NFS serving export list failure
Last modified: 2009-06-11 11:08:48 EDT
Description of problem:
When NFS serving from Fedora 10 to clients on the local network, initial exportfs fails because named running on the same server is not being used for lookups correctly. The scenario is that IP addresses for NFS client hosts on the local network are listed in the local domain server (named) tables. Due to the start order/timing issues, when exportfs is run as part of /etc/init.d/nfs start, the named is not being referred to yet and the exportfs command rejects all clients on the local subnet as having "non-inet address" (yet) and fails to enter them into the kernel NFS exports table. Re-running exportfs after server machine has finished booting, exportfs can now resolve the names using named and they get added to the export list for the NFS server.
The issue is that the as-shipped system will not boot into an operational NFS server/named server due to this problem.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Export some NFS filesystems to hosts identified by names that only appear
in the local name server tables.
2. Reboot the system
3. NFS clients will fail to mount with Permission Denied despite being listed
in the /etc/exports file due to startup ordering/timing issues.
NFS clients get Permission Denied on the mount.
NFS clients get granted access if listed in /etc/exports.
If you add the hostname in /etc/hosts, the problem happen?
I don't tried to reproduce.
I'll try adding one of the NFS clients but not the others, rebooting and reporting back on progress. Will probably be tomorrow evening before I can do that without interrupting user service.
*** This bug has been marked as a duplicate of bug 475133 ***