Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1610631

Summary: NFS4.1 very slow writes on netapp filer.
Product: Red Hat Enterprise Linux 7 Reporter: Laxminarayan <lvasamse>
Component: nfs-utilsAssignee: Steve Dickson <steved>
Status: CLOSED DUPLICATE QA Contact: Yongcheng Yang <yoyang>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.5CC: xifeng, xzhou
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-08-01 08:43: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:
Attachments:
Description Flags
tcpdump none

Description Laxminarayan 2018-08-01 05:19:27 UTC
Created attachment 1472001 [details]
tcpdump

Description of problem:

The customer has an NFS mount for backups. The same mount (which is hosted on a NetApp filer) is used by RHEL6 clients and these do not any issue. On RHEL7.5 when writing a simple file (eg. "echo test > test") it takes around 2 minutes to get the command prompt back.

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


How reproducible:

It is reproducible easily with netapp filer. 

The customer says RHEL6 do not have any a problem but I am verifying this again and update. 

[root@srdadora0233 ~]# mount -t nfs -o vers=4.1,sec=sys 192.168.112.15:/Backup_D /mnt/nfs/backup -vvv
mount.nfs: timeout set for Tue Jul 31 12:35:09 2018
mount.nfs: trying text-based options 'vers=4.1,sec=sys,addr=192.168.112.15,clientaddr=192.168.112.29'

[root@srdadora0233 ~]# mount | grep Backup_D
192.168.112.15:/Backup_D on /mnt/nfs/backup type nfs4 (rw,relatime,vers=4.1,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.112.29,local_lock=none,addr=192.168.112.15)

[root@srdadora0233 ~]# dd if=/dev/urandom of=/mnt/nfs/backup/testfile_without_cache bs=1M count=1000 oflag=direct

^C^C^C^C
2+0 records in
2+0 records out
2097152 bytes (2.1 MB) copied, 781.646 s, 2.7 kB/s

Steps to Reproduce:
1. Mount the share with nfs4.1
2. Try dd command
3.

Actual results:
The dd command should complete quickly but it takes much longer then expected. 

Expected results:


Additional info:

Comment 2 Yongcheng Yang 2018-08-01 08:43:00 UTC
Looks to me they are the same issue.

Closing this as there's customer tracker on another one.

*** This bug has been marked as a duplicate of bug 1610632 ***