| Summary: | stat information not returned from the same subvolume always | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Vikas Gorur <vikas> |
| Component: | replicate | Assignee: | Vikas Gorur <vikas> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | mainline | CC: | gluster-bugs, vinayak |
| 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: | RTNR | 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: | 761838 | ||
|
Description
Vikas Gorur
2009-07-09 17:36:13 UTC
The bug is in the various inode-write calls in replicate. They also return stat info, but do not follow the read-subvolume logic. We can easily fix this by returning stat info from the read child in all the inode-write ops too. Doing this, however, means we will lose the "quick unwind" feature, as we will have to wait until the call has returned from the read child to unwind. Is it worth it? Patch submitted: http://patches.gluster.com/patch/744/ PATCH: http://patches.gluster.com/patch/744 in master (Return stat info from read-child in all the inode-write ops) PATCH: http://patches.gluster.com/patch/744 in release-2.0 (Return stat info from read-child in all the inode-write ops) |