RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 735214 - Release note on how to get the pNFS kernel module loaded.
Summary: Release note on how to get the pNFS kernel module loaded.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Steve Dickson
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-01 20:05 UTC by Steve Dickson
Modified: 2011-10-11 17:44 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
To have pNFS functional enabled automatically create the /etc/modprobe.d/dist-nfsv41.conf file with the following line: alias nfs-layouttype4-1 nfs_layout_nfsv41_files and reboot. Now then the -o minorversion=1 mount option is specified and the server is pNFS enabled, the the pNFS client code will automatically be enabled.
Clone Of:
Environment:
Last Closed: 2011-10-11 17:44:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Steve Dickson 2011-09-01 20:05:09 UTC
Description of problem:

Something similar to the following verbiage needs
to appear in the 6.2 release notes. 

To have pNFS functional enabled automatically create
the /etc/modprobe.d/dist-nfsv41.conf file with the
following line:
     alias nfs-layouttype4-1 nfs_layout_nfsv41_files
and reboot.

Now then the -o minorversion=1 mount option is specified
and the server is pNFS enabled, the the pNFS client code
will automatically be enabled.

Comment 1 Steve Dickson 2011-09-01 20:07:06 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
To have pNFS functional enabled automatically create
the /etc/modprobe.d/dist-nfsv41.conf file with the
following line:
     alias nfs-layouttype4-1 nfs_layout_nfsv41_files
and reboot.

Now then the -o minorversion=1 mount option is specified
and the server is pNFS enabled, the the pNFS client code
will automatically be enabled.

Comment 2 RHEL Program Management 2011-09-01 20:20:23 UTC
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has 
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed 
products. This request is not yet committed for inclusion in an Update release.


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