| Summary: | NFSv3 downloads never complete | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Yaakov Selkowitz <yselkowi> |
| Component: | libnfs | Assignee: | Ross Lagerwall <ross> |
| Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 25 | CC: | alexl, oholy, ross |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-11-23 07:26:42 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: | |
|
Description
Yaakov Selkowitz
2016-11-22 08:03:20 UTC
I can reproduce it with unfsd. It stuck at the end of file and still reads 4 bytes of same data and never ends... nfs-cat uses nfs_pread and call it until offset < size, gvfs uses nfs_read_async and expects that 0 is returned at the end of file, but it isn't returned, 4 is returned... I can't reproduce it with exportfs. It sounds like bug in lower levels of libnfs, or unfsd bug. Result from rpc_nfs3_read_async seems to be wrong... Can you please file bug report for libnfs upstream? https://github.com/sahlberg/libnfs/issues And with unfs3: https://sourceforge.net/p/unfs3/bugs/9/ Thanks! So, it is probably unfs3 bug and unfs3 seems not to be in our repositories, so closing... |