Bug 820004
| Summary: | nfs client hangs older nfs servers | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Vilius Šumskas <vilius> |
| Component: | kernel | Assignee: | Jeff Layton <jlayton> |
| Status: | CLOSED NOTABUG | QA Contact: | Filesystem QE <fs-qe> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.3 | CC: | jcpunk, jlayton, kzhang, rwheeler, steved, torel |
| 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-12-11 11:09:51 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
Vilius Šumskas
2012-05-08 20:46:30 UTC
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux. The issue still persist in kernel-2.6.32-279.el6.x86_64 in RHEL 6.3 release. Can someone take a look into it? cc Could you please get a network trace on whats going over the wire? Something similar to: tshark -w /tmp/data.pcap host <server> bzip2 /tmp/data.pcap Here you go http://www.tekila.lt/public/data.pcap.bz2 The capture was made just right after rebooted to RHEL 6.3 kernel, started to upload data through FTP to NFS share, and then NFS server hang. Hmmm...sounds more like a problem with the server here. Even if the client is doing something it doesn't like, hanging is not really a good way to handle it. Perhaps you should consider getting Apple's support organization involved? I completely support your statement that hanging is not a really good way to handle it, but if something can be done on the client side to make it more compatible with Apple (and other) products, it would be great. I can try to report this to Apple, but their support is beyond terrible when it goes to server products. The response times are YEARS (literally) and their standard response is "we don't support versions other than the current version". Even for the companies with support contracts. To be clear, we're happy to help, but without some idea of why the server is hanging, it's going to end up being a game of "try this and see if it works", if we can even come up with things to try... What you might also want to do is to get a capture of some of the network traffic between the client and server for the "working" case as well so you can compare and contrast between the two. A working case capture with RHEL 6.1 kernel: http://www.tekila.lt/public/data_working.pcap.bz2 (In reply to comment #10) > A working case capture with RHEL 6.1 kernel: > http://www.tekila.lt/public/data_working.pcap.bz2 Unfortunately I don't see the hang in that trace... But I do see a number of [TCP previous segment lost] packages which might point to a network issue... I have already ruled that out changing the router. Even if it is network problem, it doesn't explain why server works in 6.1 kernel and doesn't work in 6.3. Whether Apple's support is terrible or not, a hung server indicates a bug in the server. A network server of any sort ought to be able to handle anything the client throws at it without hanging. I've looked over the captures and I don't see anything wrong with what's being sent to the server here. Without more to go on, I don't see anything that we can do. At this point, I'm going to call this a bug in Apple's product and close this as NOTABUG. If you can get their support organization involved, and they point out something wrong with what we're sending to them then please reopen this can we'll be happy to take another look. Also, with complex multi-vendor cases like this, it's generally a good idea to open a support case with RH support. |