REVIEW: http://review.gluster.org/15166 (snapshot/uss: log is filled with gfid is NULL error) posted (#2) for review on release-3.8 by Rajesh Joseph (rjoseph)
REVIEW: http://review.gluster.org/15170 (snapshot/uss: client log is filled with "invalid argument: inode" error) posted (#2) for review on release-3.8 by Rajesh Joseph (rjoseph)
REVIEW: http://review.gluster.org/15171 (snapshot/uss: client-side log is filled with "invalid-argument" error) posted (#2) for review on release-3.8 by Rajesh Joseph (rjoseph)
COMMIT: http://review.gluster.org/15166 committed in release-3.8 by Atin Mukherjee (amukherj) ------ commit 03003d14e4f052db278aa4edf47cf3b98779ca33 Author: Rajesh Joseph <rjoseph> Date: Tue May 24 15:10:33 2016 +0530 snapshot/uss: log is filled with gfid is NULL error In snapview-server if the lookup came on missing entry then it does not have proper context to see if it is the case of "Stale file handle" or ENOENT. We should not log this error in GF_LOG_ERROR level, instead this should be a debug log. > BUG: 1339149 > Signed-off-by: Rajesh Joseph <rjoseph> > Reviewed-on: http://review.gluster.org/14514 > Smoke: Gluster Build System <jenkins.com> > NetBSD-regression: NetBSD Build System <jenkins.org> > CentOS-regression: Gluster Build System <jenkins.com> > Reviewed-by: Jeff Darcy <jdarcy> (cherry picked from commit dca1c08c6384e34403d8b5ad6eaf0931529168ac) BUG: 1367297 Signed-off-by: Rajesh Joseph <rjoseph> Change-Id: I8f7cc0e117e9a6dd9482da2e94a56f2ed731a442 Reviewed-on: http://review.gluster.org/15166 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Avra Sengupta <asengupt> Reviewed-by: Atin Mukherjee <amukherj>
COMMIT: http://review.gluster.org/15171 committed in release-3.8 by Niels de Vos (ndevos) ------ commit c23a651b7e9fce8a51e3d9656cc64a49ff42aef7 Author: Rajesh Joseph <rjoseph> Date: Tue May 24 14:33:54 2016 +0530 snapshot/uss: client-side log is filled with "invalid-argument" error xdata is used without checking if it is NULL or not. > BUG: 1339149 > Signed-off-by: Rajesh Joseph <rjoseph> > Reviewed-on: http://review.gluster.org/14511 > Smoke: Gluster Build System <jenkins.com> > Reviewed-by: Raghavendra Talur <rtalur> > CentOS-regression: Gluster Build System <jenkins.com> > NetBSD-regression: NetBSD Build System <jenkins.org> (cherry picked from commit f55a973e581aaa25bbe38be83e007e1b2eaed659) BUG: 1367297 Signed-off-by: Rajesh Joseph <rjoseph> Change-Id: Ib6ddaab28ec3b430b8d646aada0456d3cc9978cb Reviewed-on: http://review.gluster.org/15171 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Avra Sengupta <asengupt> Reviewed-by: Niels de Vos <ndevos>
COMMIT: http://review.gluster.org/15170 committed in release-3.8 by Niels de Vos (ndevos) ------ commit 6fde5e3411d44c752d81006d35f19e92e23441af Author: Rajesh Joseph <rjoseph> Date: Tue May 24 19:14:41 2016 +0530 snapshot/uss: client log is filled with "invalid argument: inode" error svc_inode_ctx_get is called even if inode is NULL. We should not call this function if inode is NULL > BUG: 1339149 > Signed-off-by: Rajesh Joseph <rjoseph> > Reviewed-on: http://review.gluster.org/14525 > Smoke: Gluster Build System <jenkins.com> > NetBSD-regression: NetBSD Build System <jenkins.org> > CentOS-regression: Gluster Build System <jenkins.com> > Reviewed-by: Jeff Darcy <jdarcy> (cherry picked from commit edcc6a4ef4f39d5e3073195d45011e3cdfa7c091) BUG: 1367297 Signed-off-by: Rajesh Joseph <rjoseph> Change-Id: I5c3f17633ca88e5b6f40d4acf14a09e14b7ef62b Reviewed-on: http://review.gluster.org/15170 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Tested-by: Avra Sengupta <asengupt> Reviewed-by: Avra Sengupta <asengupt> 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.8.3, please open a new bug report. glusterfs-3.8.3 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://www.gluster.org/pipermail/announce/2016-August/000059.html [2] https://www.gluster.org/pipermail/gluster-users/