Bug 825009

Summary:	NFSv4.1: Add LAYOUTRETURN support
Product:	Red Hat Enterprise Linux 6	Reporter:	Steve Dickson <steved>
Component:	kernel	Assignee:	Steve Dickson <steved>
Status:	CLOSED ERRATA	QA Contact:	Jian Li <jiali>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4	CC:	jiali, kzhang, nmurray, rwheeler, salmy
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	pNFS
Fixed In Version:	kernel-2.6.32-288.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-21 06:15:00 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Steve Dickson 2012-05-24 19:54:57 UTC

Description of problem:
For RHEL6 to continue to be relevant in the pNFS world, certain features needed to be backported. The support of LAYOUTRETURNs is one of those features. It has the potential of allowing the client to support multiple layout types.    

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 3 RHEL Program Management 2012-06-27 13:44:57 UTC

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.

Comment 4 Jian Li 2012-07-04 08:00:35 UTC

pnfs regression test is needed, and only file layout is not enough, block or object layout is needed to test.

Comment 5 Jarod Wilson 2012-07-23 17:16:32 UTC

Patch(es) available on kernel-2.6.32-288.el6

Comment 9 errata-xmlrpc 2013-02-21 06:15:00 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-0496.html