Bug 618759 - Auto-configuration of NFSv4 pseudofilesystem
Summary: Auto-configuration of NFSv4 pseudofilesystem
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: nfs-utils   
(Show other bugs)
Version: 5.5
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Steve Dickson
QA Contact: yanfu,wang
Keywords: FutureFeature
Depends On:
Blocks: 586461
TreeView+ depends on / blocked
Reported: 2010-07-27 16:49 UTC by Lon Hohberger
Modified: 2016-04-26 13:50 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 586461
Last Closed: 2010-09-21 20:24:52 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Lon Hohberger 2010-07-27 16:49:49 UTC
+++ 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 lhh@redhat.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 lhh@redhat.com 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:

 - kernel
 - nfs-utils
 - rgmanager

Additionally, for consistency, the following packages should be updated

 - conga 
 - system-config-cluster (primarily for schema purposes)

Comment 5 RHEL Product and Program Management 2010-09-21 20:24:52 UTC
Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.

Note You need to log in before you can comment on or make changes to this bug.