+++ This bug was initially created as a clone of Bug #264661 +++ --- Additional comment from lars on 2011-04-01 16:13:45 EDT --- We've just run into this problem on two of our RHEL5.5 systems. That is, systems that had previously been exporting NFS filesystems without a problem suddenly started reporting "permission denied" despite entries like this in /etc/exports: /mnt/somefilesystem *(ro) The solution was to manually mount /proc/fs/nfsd. /etc/modprobe.d/modprobe.conf.dist is unmodified from the stock configuration and includes the necessary install/remove rules: install nfsd /sbin/modprobe --first-time --ignore-install nfsd && { /bin/mount -t nfsd nfsd /proc/fs/nfsd > /dev/null 2>&1 || :; } remove nfsd { /bin/umount /proc/fs/nfsd > /dev/null 2>&1 || :; } ; /sbin/modprobe -r --first-time --ignore-remove nfsd This happened on unrelated systems, maintained by two distinct groups of people. Since the mount operation is idempotent (if the filesystem is already mounted, running "mount -t nfsd nfsd /proc/fs/nfsd" simply reports an error), we've simply made this part of the NFS startup script. It seems that this might be a good idea in general.
Could this possibly be a Selinux issue? Does setenfore 0 make the problem go away?
Pretty sure that SELinux was off on the systems. Lars, do you remember which machines these were?
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release.
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.