path: root/xlators/storage
diff options
authorKrishnan Parthasarathi <>2014-09-03 10:29:07 +0530
committerKaushal M <>2014-09-03 03:16:44 -0700
commit2c4c1918e3a65f1b8a30b2e321c325c3c3aed950 (patch)
tree1027e1501d6c76c7cf43b33c8afc7edf72953c9b /xlators/storage
parent312b339190b7b8f2e38cdd210bf2ee71e53b287e (diff)
glusterd: Improve debugging experience for glusterd locks
Today, when glusterd's internal locking mechanism fails with invalid type or when another competing lock is being held, the log message doesn't provide enough information directly as to which command saw this (first). Following is a snippet of how a failure would look in the log file. This would greatly assist in debugging. [2014-09-03 04:57:58.549418] E [glusterd-locks.c:520:glusterd_mgmt_v3_lock] (-->/usr/local/lib/glusterfs/3.7dev/xlator/mgmt/ [0x7f30b071e651] (-->/usr/local/lib/glusterfs/3.7dev/xlator/mgmt/ [0x7f30b072e19c] (-->/usr/local/lib/glusterfs/3.7dev/xlator/mgmt/ [0x7f30b072de6d]))) 0-management: Invalid entity. Cannot perform locking operation on vol types Change-Id: I0595f49d60e620e8b065f3506bdb147ccee383a7 Signed-off-by: Krishnan Parthasarathi <> Reviewed-on: Reviewed-by: Atin Mukherjee <> Tested-by: Gluster Build System <> Reviewed-by: Kaushal M <>
Diffstat (limited to 'xlators/storage')
0 files changed, 0 insertions, 0 deletions