Bug 800833
Summary: | ENOENT while deleting and creating the same file again | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Anush Shetty <ashetty> |
Component: | stat-prefetch | Assignee: | Raghavendra G <rgowdapp> |
Status: | CLOSED UPSTREAM | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | mainline | CC: | gluster-bugs |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-04-27 04:02:19 UTC | Type: | --- |
Regression: | --- | Mount Type: | fuse |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Anush Shetty
2012-03-07 11:15:14 UTC
with non-zero timeouts, its expected that md-cache can go out of sync. In this case, lookup call is served from stale cache (cache rendered stale by unlink of file from another client) there by resulting in ENOENT errors. If some one wants zero tolerance towards stale-caches, they can use timeout value 0. Closing this bug, since its a known issue. *** Bug 800822 has been marked as a duplicate of this bug. *** Since we see this issue even when md-cache timeout is 0, reopening this bug. This issue is not seen anymore. |