Red Hat Bugzilla – Bug 618759
Auto-configuration of NFSv4 pseudofilesystem
Last modified: 2016-04-26 09:50:32 EDT
+++ This bug was initially created as a clone of Bug #586461 +++
Description of problem:
The NFS service within cluster suite does not allow for the NFS version to be specified. Thus the service defaults to the RHEL default of v3.
If NFSv4 is required the script resource or another customer solution must be employed.
It also stands to reason that in certain circumstances you might wish to change some of the other defaults like rsize and wsize.
So perhaps it would make sense to change the NFS agent so that any nfs configuration option could be implemented.
[some details removed for the sake of brevity]
--- Additional comment from email@example.com on 2010-07-27 10:18:38 EDT ---
In RHEL6 there is a kernel enhancement which makes this feasible - it sets up the pseudoroot namespace when the first export is fed in. This in turn allows 'exportfs' to work largely as it does today.
Actually, we added NFSv4 support to RHEL6:
On RHEL5, setting up the NFSv4 server requires setting up a pseudo-root file system explicitly, which is not particularly easy to do in a sane way in a cluster with more than one export.
More to the point, any work done on RHEL5 will not work on RHEL6 and vice-versa due to differences in the way NFSv4 setup is performed in those releases. There is also no sane way to do configuration upgrade compatibility - users of a resource-agent designed for RHEL5 would have no migration path; it would be a dead-end feature.
So, we'd need the kernel enhancement from RHEL6 backported to RHEL5 before this is feasible.
--- Additional comment from firstname.lastname@example.org on 2010-07-27 12:44:46 EDT ---
I scoped this out with one of the developers who implemented the kernel feature. The following packages will require changes in order for the cluster to provide a native nfsv4 agent on Red Hat Enterprise Linux 5:
Additionally, for consistency, the following packages should be updated
- system-config-cluster (primarily for schema purposes)
Development Management has reviewed and declined this request. You may appeal
this decision by reopening this request.