Bug 2230456

Summary:	NFSv4.1 client incorrectly sets up trunked connection when MDS=DS
Product:	Red Hat Enterprise Linux 9	Reporter:	Olga Kornieskaia <kolga>
Component:	kernel	Assignee:	Red Hat Kernel Manager <kernel-mgr>
kernel sub component:	NFS	QA Contact:	Red Hat Kernel QE team <kernel-qe>
Status:	CLOSED MIGRATED	Docs Contact:
Severity:	unspecified
Priority:	unspecified	Keywords:	MigratedToJIRA
Version:	9.3	Flags:	pm-rhel: mirror+
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-23 12:06:40 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 Olga Kornieskaia 2023-08-09 13:39:29 UTC

Description of problem:

When an NFSv4.1 client is doing pnfs IO, it gets a layout with deviceid where data is located, then does GETDEVICEINFO where the server returns it a list of IPs over which the client can do trunking to the data server. However when MDS=DS, then client incorrectly throws away the first entry in the getdeviceinfo list and then doing IO over the other connections.

An upstream patch was submitted to fix it: "NFSv4.1: fix pnfs MDS=DS session trunking". Will update when I have a commit id.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 RHEL Program Management 2023-09-23 12:04:15 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 2 RHEL Program Management 2023-09-23 12:06:40 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.