Bug 1583462
| Summary: | Sharding sends all application sent fsyncs to the main shard file | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Sunil Kumar Acharya <sheggodu> | |
| Component: | sharding | Assignee: | Krutika Dhananjay <kdhananj> | |
| Status: | CLOSED ERRATA | QA Contact: | SATHEESARAN <sasundar> | |
| Severity: | high | Docs Contact: | ||
| Priority: | medium | |||
| Version: | rhgs-3.3 | CC: | amukherj, bugs, kdhananj, nbalacha, nchilaka, pmulay, rcyriac, rhinduja, rhs-bugs, sabose, sankarshan, sasundar, storage-qa-internal | |
| Target Milestone: | --- | Keywords: | ZStream | |
| Target Release: | RHGS 3.3.1 Async | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | glusterfs-3.8.4-54.12 | Doc Type: | Bug Fix | |
| Doc Text: |
Previously, when an application sent fsync on a sharded file, the shards associated with the file were not being synced to disk. Hence, potentially causing data loss in case of a plain distribute shard volume. This update fixes the shard translator by syncing all the modified shards to disk whenever the application sends an fsync.
|
Story Points: | --- | |
| Clone Of: | 1493085 | |||
| : | 1585104 (view as bug list) | Environment: | ||
| Last Closed: | 2018-07-19 06:00:07 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | 1468483, 1493085 | |||
| Bug Blocks: | 1523608, 1585104 | |||
|
Comment 4
Atin Mukherjee
2018-06-25 12:54:31 UTC
Tested with glusterfs-3.8.4-54.13.el7rhgs with the following steps: 1. Created few VMs with their images on the distribute volume 2. Started all the VMs and installed OS on them. 3. Triggered lot of fsyncs inside the VM 4. Ran I/O inside them for few hours There were no issues seen. Not the requestee but the doc text seems a little too technical. I do not understand the impact of not having this fix in the code to the end user. Were distribute volumes supported in earlier releases? If not, perhaps the doc text is not required at all. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:2222 |