| Summary: | NFS client has troubles with fileid with bit 31 (or bit 63) set | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | IBM Bug Proxy <bugproxy> |
| Component: | nfs-utils | Assignee: | Jeff Layton <jlayton> |
| Status: | CLOSED DUPLICATE | QA Contact: | yanfu,wang <yanwang> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.1 | CC: | balkov, jkachuck, jlayton, steved, syeghiay |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-05-26 11:27:14 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 684385, 684953 | ||
|
Description
IBM Bug Proxy
2011-04-11 18:30:36 UTC
(In reply to comment #0) > ---Problem Description--- > NFS client has troubles with fileid with bit 31 (or bit 63) set Could you please define "troubles"? Is something failing, oops-ing? Are error messages being logged? > > ---Steps to Reproduce--- > run telldir test case on a server that produces fileids with bit 31 set I'm assuming this is the cthon special test. Is there an error message? What are given args to create the error? > > Architecture and OS of the NFS client: RHEL 5.5 i386 Is this a RHEL5 problem? If so why is the bz opened against 6.1? ------- Comment From ffilz.com 2011-04-11 17:54 EDT------- This was discovered on RHEL 5.5, but is also an upstream bug, and therefore assumed to be in RHEL 6 also. Jeff Layton and Joe Kachuck asked for IBM bug 68522, RIT1613663, to be cloned for RHEL 6. Please see the other bug for full details. This patch got pulled in as part of a larger pNFS update, so closing this as a duplicate of that bug. *** This bug has been marked as a duplicate of bug 701373 *** |