Hi,
[2015-08-03 14:51:57.791081] E [glusterd-utils.c:148:glusterd_lock]
0-management: Unable to get lock for uuid:
76e4398c-e00a-4f3b-9206-4f885c4e5206, lock held by:
76e4398c-e00a-4f3b-9206-4f885c4e5206
This indicates that cluster is still operating at older op version. You would
Could you check the glusterd log at the other nodes, that would give you
the hint of the exact issue. Also looking at .cmd_log_history will give you
the time interval at which volume status commands are executed. If the gap
is in milisecs then you are bound to hit it and its expected.
-Atin
Sent
atin.mukherje...@gmail.com
Sent: 03 August 2015 15:22
To: Osborne, Paul (paul.osbo...@canterbury.ac.uk)
Cc: gluster-users@gluster.org
Subject: Re: [Gluster-users] Locking failed - since upgrade to 3.6.4
Could you check the glusterd log at the other nodes, that would give you the
hint of the exact
Mukherjee atin.mukherje...@gmail.com
Sent: 03 August 2015 15:22
To: Osborne, Paul (paul.osbo...@canterbury.ac.uk)
Cc: gluster-users@gluster.org
Subject: Re: [Gluster-users] Locking failed - since upgrade to 3.6.4
Could you check the glusterd log at the other nodes, that would give you
