Bug 1437763
| Summary: | File-level WORM allows ftruncate() on read-only files | |||
|---|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Geunmoon Oh <gm06041> | |
| Component: | unclassified | Assignee: | Karthik U S <ksubrahm> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
| Severity: | unspecified | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 3.10 | CC: | amukherj, bugs, ksubrahm, rtalur | |
| Target Milestone: | --- | Keywords: | Triaged | |
| Target Release: | --- | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | worm | |||
| Fixed In Version: | glusterfs-3.10.2 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1438810 1439112 (view as bug list) | Environment: | ||
| Last Closed: | 2017-05-31 20:47: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: | 1438810 | |||
| Bug Blocks: | 1439112, 1442603 | |||
|
Description
Geunmoon Oh
2017-03-31 06:17:22 UTC
i corrected some explanation. Actual results: - the file was truncated. Related github issue: https://github.com/gluster/glusterfs/issues/123 REVIEW: https://review.gluster.org/16999 (features/worm: Adding implementation for ftruncate) posted (#1) for review on release-3.10 by Karthik U S (ksubrahm) COMMIT: https://review.gluster.org/16999 committed in release-3.10 by Shyamsundar Ranganathan (srangana) ------ commit 0090727aea9dfcfdd06debadeb5cf9377adca64f Author: karthik-us <ksubrahm> Date: Tue Apr 4 18:57:32 2017 +0530 features/worm: Adding implementation for ftruncate Problem: Since the ftruncate fop was not handled in the worm feature, when truncate and write was happening on a worm-retained/worm file, it was giving the EROFS error but truncating the file, which is not correct. > Change-Id: I1a7e904655210d78bce9e01652ac56f3783b5aed > BUG: 1438810 > Signed-off-by: karthik-us <ksubrahm> > Reviewed-on: https://review.gluster.org/16995 > NetBSD-regression: NetBSD Build System <jenkins.org> > Reviewed-by: Niels de Vos <ndevos> > CentOS-regression: Gluster Build System <jenkins.org> > Reviewed-by: Ravishankar N <ravishankar> > Smoke: Gluster Build System <jenkins.org> > Reviewed-by: Amar Tumballi <amarts> > Reviewed-by: Raghavendra Talur <rtalur> (cherry picked from commit c5a4a77848024d2adf8cd4f35d550ba90c174fc7) Change-Id: I815049d37d95597021e11b1e3d25d56bb83623c4 BUG: 1437763 Signed-off-by: karthik-us <ksubrahm> Reviewed-on: https://review.gluster.org/16999 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Ravishankar N <ravishankar> Reviewed-by: jiffin tony Thottan <jthottan> Reviewed-by: Shyamsundar Ranganathan <srangana> This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.10.2, please open a new bug report. |