| Summary: | ls -lh on NFS mount of 2-mirror replicate gives incorrect file size | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Shehjar Tikoo <shehjart> |
| Component: | replicate | Assignee: | shishir gowda <sgowda> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | nfs-alpha | CC: | amarts, gluster-bugs, nsathyan, vijay |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | RTP | Mount Type: | nfs |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Shehjar Tikoo
2010-07-20 03:39:21 UTC
During dd IO on a file that resides on the NFS mount point, which is in fact a replicated backend, say one replica goes down and comes back up only after dd has finished. The situation will result in an inconsistent file on one node and a consistent one on the mirror that was always up. If we do ls -lh on the NFS mount after the dd completes and with the failed node now back up, the ls -lh returns the file size from the inconsistent replica. Setting mount type to nfs to help me keep track of bugs reported in components outside gnfs but seen over an nfs mount as compared to the fuse mount. issue with metadata self heal not being done properly. PATCH: http://patches.gluster.com/patch/5086 in master (replicate: keep read_child in inode ctx as up-to-date as possible) PATCH: http://patches.gluster.com/patch/6054 in master (replicate: set read-child to the subvolume which replied first (fastest)) |