+++ This bug was initially created as a clone of Bug #1382266 +++ Description of problem: In case if there is open() done on a file with O_TRUNC posix flag passed, the backend server truncates the file, resulting in change of size of the file. This case needs to be handled by md-cache and should invalidate its cache-entry accordingly. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: --- Additional comment from Worker Ant on 2016-10-06 03:47:11 EDT --- REVIEW: http://review.gluster.org/15618 (md-cache: Invalidate cache entry for open() with O_TRUNC) posted (#1) for review on master by soumya k (skoduri) --- Additional comment from Worker Ant on 2016-10-10 09:12:30 EDT --- REVIEW: http://review.gluster.org/15618 (md-cache: Invalidate cache entry for open() with O_TRUNC) posted (#2) for review on master by soumya k (skoduri) --- Additional comment from Worker Ant on 2016-10-10 09:48:39 EDT --- REVIEW: http://review.gluster.org/15618 (md-cache: Invalidate cache entry for open() with O_TRUNC) posted (#3) for review on master by soumya k (skoduri) --- Additional comment from Worker Ant on 2016-10-14 06:46:40 EDT --- REVIEW: http://review.gluster.org/15618 (md-cache: Invalidate cache entry for open() with O_TRUNC) posted (#4) for review on master by soumya k (skoduri) --- Additional comment from Worker Ant on 2016-10-27 01:46:36 EDT --- COMMIT: http://review.gluster.org/15618 committed in master by Raghavendra G (rgowdapp) ------ commit 6ca5d6382f03685b31b12accb095093cf1486603 Author: Soumya Koduri <skoduri> Date: Thu Oct 6 13:13:44 2016 +0530 md-cache: Invalidate cache entry for open() with O_TRUNC When a file is opened with O_TRUNC flag set, its size gets set to '0'. This case needs to be handled in md-cache to avoid sending incorrect cached stat. Change-Id: I95d1f8a6634734898883ede010c3e7b0b7eb97d9 BUG: 1382266 Signed-off-by: Soumya Koduri <skoduri> Reviewed-on: http://review.gluster.org/15618 Smoke: Gluster Build System <jenkins.org> Reviewed-by: jiffin tony Thottan <jthottan> Tested-by: jiffin tony Thottan <jthottan> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Kaleb KEITHLEY <kkeithle>
REVIEW: http://review.gluster.org/15770 (md-cache: Invalidate cache entry for open() with O_TRUNC) posted (#1) for review on release-3.9 by soumya k (skoduri)
COMMIT: http://review.gluster.org/15770 committed in release-3.9 by Raghavendra G (rgowdapp) ------ commit 0c908b6c03f6e5e050a49d2c49505dc7cd8efbbc Author: Soumya Koduri <skoduri> Date: Thu Oct 6 13:13:44 2016 +0530 md-cache: Invalidate cache entry for open() with O_TRUNC When a file is opened with O_TRUNC flag set, its size gets set to '0'. This case needs to be handled in md-cache to avoid sending incorrect cached stat. This is backport of below mainline patch - http://review.gluster.org/#/c/15618/ > Change-Id: I95d1f8a6634734898883ede010c3e7b0b7eb97d9 > BUG: 1382266 > Signed-off-by: Soumya Koduri <skoduri> > Reviewed-on: http://review.gluster.org/15618 > Smoke: Gluster Build System <jenkins.org> > Reviewed-by: jiffin tony Thottan <jthottan> > Tested-by: jiffin tony Thottan <jthottan> > NetBSD-regression: NetBSD Build System <jenkins.org> > CentOS-regression: Gluster Build System <jenkins.org> > Reviewed-by: Kaleb KEITHLEY <kkeithle> > (cherry picked from commit 6ca5d6382f03685b31b12accb095093cf1486603) Change-Id: I9780a4051adaa9030bd33da68dbc0a31212de054 BUG: 1391448 Signed-off-by: Soumya Koduri <skoduri> Reviewed-on: http://review.gluster.org/15770 Reviewed-by: jiffin tony Thottan <jthottan> Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Kaleb KEITHLEY <kkeithle>
This bug is getting closed because GlusterFS-3.9 has reached its end-of-life [1]. Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS. If this bug still exists in newer GlusterFS releases, please open a new bug against the newer release. [1]: https://www.gluster.org/community/release-schedule/