Bug 805660
Summary: | System freezes during large NFS transfers after kernel-2.6.18-308.1.1.el5 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Eric Schewe <eric.schewe> |
Component: | nfs-utils | Assignee: | nfs-maint |
Status: | CLOSED DUPLICATE | QA Contact: | Red Hat Kernel QE team <kernel-qe> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 5.8 | CC: | eric.schewe, jadavis6, jlayton, rwheeler, steved |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-06-12 18:48:13 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Eric Schewe
2012-03-21 18:35:17 UTC
Hi Eric, If you have a Red Hat support contract, please work with our support team to help gather information, etc. Thanks for the bug report! And if I do not? FWIW we (North Carolina Agricultural and Technical State) are having the same exact issue. We do have a support contract through the State of North Carolina and I'm working one finding a point of contact. I have network traces from the period of the hang I can attach if you want, but it may be a bit until UNC-GA gets back to me with how they want us to escalate this up to you guys. Would it be possible to leave this Bugzilla open or would I have to create a new one? (In reply to comment #0) > > > Steps to Reproduce: > 1. Boot system using kernel-2.6.18-308.1.1.el5 > 2. Execute backup script that copies the contents from the client NFS systems > to the NFS server. > > Actual results: > System freezes > > Expected results: > System to remain functional and copy operation to complete > > Additional info: > NFS Clients /etc/fstab > nfsserver.hostname:/ /mnt/nfsExport nfs4 > rw,_netdev,sync,hard,intr,rsize=8192,wsize=8192 I'm noticing you are using v4.... Just curious does the freeze happen with v3? > > NFS Server /etc/fstab > <local path> <local mount> none bind 0 0 > > NFS Server /etc/exports > <local path> <remote host > fqdn>(rw,sync,no_wdelay,all_squash,nohide,no_subtree_check,fsid=0) > <local path>/backups <remote host > fqdn>(rw,sync,no_wdelay,no_root_squash,nohide,no_subtree_check) Is the server also running a 308.1.1.el5 kernel? (In reply to comment #2) > And if I do not? If you don't have a customer support arrangement, the right thing to do is to follow up with the NFS community on the upstream lists or your (other) vendor. (In reply to comment #4) > (In reply to comment #0) > > > > > > Steps to Reproduce: > > 1. Boot system using kernel-2.6.18-308.1.1.el5 > > 2. Execute backup script that copies the contents from the client NFS systems > > to the NFS server. > > > > Actual results: > > System freezes > > > > Expected results: > > System to remain functional and copy operation to complete > > > > Additional info: > > NFS Clients /etc/fstab > > nfsserver.hostname:/ /mnt/nfsExport nfs4 > > rw,_netdev,sync,hard,intr,rsize=8192,wsize=8192 > I'm noticing you are using v4.... Just curious does the freeze happen with v3? > > > > > NFS Server /etc/fstab > > <local path> <local mount> none bind 0 0 > > > > NFS Server /etc/exports > > <local path> <remote host > > fqdn>(rw,sync,no_wdelay,all_squash,nohide,no_subtree_check,fsid=0) > > <local path>/backups <remote host > > fqdn>(rw,sync,no_wdelay,no_root_squash,nohide,no_subtree_check) > Is the server also running a 308.1.1.el5 kernel? We have not tried switching from v4 to v3. Since these systems are production and I don't have any spare, identical hardware I can't really experiment. I'll try using a VM and see if I can replicate the problem and then switch to V3. The NFS server is still running 2.6.18-308.1.1.el5. We only had to revert NFS clients. I've changed the assignment of this from the kernel team to the nfs-utils team? Is that what you meant by "..the right thing to do is to follow up with the NFS community on the upstream lists.." This issue appears to have been resolved as of kernel 2.6.18-308.4.1.el5 and 2.6.18-308.8.2.el5. Sounds likely that this is a duplicate of bug 799941. *** This bug has been marked as a duplicate of bug 799941 *** |