Bug 35435
Summary: | ls of nfs mounted directory return no such file or directory error message | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Roberto Turra <r_turra> |
Component: | nfs-utils | Assignee: | Pete Zaitcev <zaitcev> |
Status: | CLOSED WORKSFORME | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.2 | CC: | mikev |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-08-01 17:43:43 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
Roberto Turra
2001-04-10 09:24:42 UTC
There's not much detail here, so I can only guess. With AFS and NFS at least, there is no guarentee of consistency between the client and server, or between two clients. In order to understand if this is a real problem, or just an misunderstanding about NFS and AFS inter-node consistancy constraints, I need to have a concrete example of the set of operations performed on the server and clients, and the order in which they were performed. If the problem becomes reproducible, a tcpdump or ethereal trace would be quite useful as well. Closing at customer's request. |