Description of problem:
It is possible that some xlators don't print debug/trace logs even when required.
In such cases debugging an existing setup without recompiling becomes very difficult. If libglusterfs/gluster wind/unwind had a debug log builtin then such dependency on every xlator would be reduced.
Version-Release number of selected component (if applicable):
mainline and all previous versions
REVIEW: http://review.gluster.org/13448 (libglusterfs: Add debug and trace logs for stack trace) posted (#3) for review on master by Raghavendra Talur (firstname.lastname@example.org)
COMMIT: http://review.gluster.org/13448 committed in master by Vijay Bellur (email@example.com)
Author: Raghavendra Talur <firstname.lastname@example.org>
Date: Mon Feb 15 18:16:04 2016 +0530
libglusterfs: Add debug and trace logs for stack trace
It has become very difficult to identify the xlator which returned
negative op_ret. Being able to just change the log level and
visualize the stack is helpful in such cases.
Signed-off-by: Raghavendra Talur <email@example.com>
CentOS-regression: Gluster Build System <firstname.lastname@example.org>
NetBSD-regression: NetBSD Build System <email@example.com>
Smoke: Gluster Build System <firstname.lastname@example.org>
Reviewed-by: Jeff Darcy <email@example.com>
Reviewed-by: Rajesh Joseph <firstname.lastname@example.org>
Reviewed-by: Vijay Bellur <email@example.com>
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.0, please open a new bug report.
glusterfs-3.8.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.