Description of problem: Same as subject I found this while testing another change, where the anon fd ctx in posix xl was already initialised by the time a write fop came in (and posix_writev() is where I was expecting the initialisation to have happened). Turns out the initialisation was being done in posix_fgetxattr() when the fop requested by shard was writev(). I traced the call and found that it is being wound by worm translator as part of writev() even though it was disabled on my setup (default configuration). With server side translators, if they are disabled, they should simply pass fop requested by the parent down to their child(ren) without doing anything else. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/14182 (features/worm: When disabled, worm xl must directly pass fops to its child xl) posted (#1) for review on master by Krutika Dhananjay (kdhananj)
REVIEW: http://review.gluster.org/14182 (features/worm: When disabled, worm xl must directly pass fops to its child xl) posted (#2) for review on master by Karthik U S (ksubrahm)
REVIEW: http://review.gluster.org/14182 (features/worm: When disabled, worm xl must directly pass fops to its child xl) posted (#3) for review on master by Karthik U S (ksubrahm)
REVIEW: http://review.gluster.org/14182 (features/worm: When disabled, worm xl must directly pass fops to its child xl) posted (#4) for review on master by Karthik U S (ksubrahm)
REVIEW: http://review.gluster.org/14182 (features/worm: When disabled, worm xl must directly pass fops to its child xl) posted (#5) for review on master by Karthik U S (ksubrahm)
COMMIT: http://review.gluster.org/14182 committed in master by Niels de Vos (ndevos) ------ commit e3fd1c1b7d9357161fd0ffe05e2617db1b9ffcd7 Author: Krutika Dhananjay <kdhananj> Date: Tue May 3 14:29:45 2016 +0530 features/worm: When disabled, worm xl must directly pass fops to its child xl Change-Id: I56ea46c2743636ef7af5c85469cb2e186eadf21f BUG: 1332460 Signed-off-by: Krutika Dhananjay <kdhananj> Reviewed-on: http://review.gluster.org/14182 Smoke: Gluster Build System <jenkins.com> Reviewed-by: Joseph Fernandes NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.com> Reviewed-by: Niels de Vos <ndevos>
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.9.0, please open a new bug report. glusterfs-3.9.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/gluster-users/2016-November/029281.html [2] https://www.gluster.org/pipermail/gluster-users/