search for: glusterd_mgmt_v3_unlock

Displaying 20 results from an estimated 33 matches for "glusterd_mgmt_v3_unlock".

Did you mean: glusterd_mgmt_v3_lock
Gluster clients can't see directories that exist or are created within a mounted volume, but can enter them.
2017 Nov 07
0
Gluster clients can't see directories that exist or are created within a mounted volume, but can enter them.
...provide the gluster volume info. Do you see any errors in the client mount log file (/var/log/glusterfs/var-lib-mountedgluster.log)? root at int-gluster-01:/var/log/glusterfs # grep 'dev_static' *.log|grep -v cmd_history glusterd.log:[2017-11-05 22:37:06.934787] W [glusterd-locks.c:675:glusterd_mgmt_v3_unlock] (-->/usr/lib64/glusterfs/3.12.2/xlator/mgmt/glusterd.so(+0x22e5a) [0x7f5047169e5a] -->/usr/lib64/glusterfs/3.12.2/xlator/mgmt/glusterd.so(+0x2cdc8) [0x7f5047173dc8] -->/usr/lib64/glusterfs/3.12.2/xlator/mgmt/glusterd.so(+0xe372a) [0x7f504722a72a] ) 0-management: Lock for vol dev_static no...
Failure while upgrading gluster to 3.10.1
2017 May 29
1
Failure while upgrading gluster to 3.10.1
...7f767c239c8e] (--> /usr/lib/x86_64-linux-gnu/ > libgfrpc.so.0(rpc_clnt_notify+0x88)[0x7f767c23a4a8] ))))) 0-management: > forced unwinding frame type(GLUSTERD-DUMP) op(DUMP(1)) called at 2017-05-29 > 11:04:52.183210 (xid=0x23419) > [2017-05-29 11:04:52.183735] W [glusterd-locks.c:681:glusterd_mgmt_v3_unlock] > (-->/usr/lib/x86_64-linux-gnu/glusterfs/3.7.9/xlator/mgmt/ > glusterd.so(glusterd_big_locked_notify+0x4b) [0x7f767734dffb] > -->/usr/lib/x86_64-linux-gnu/glusterfs/3.7.9/xlator/mgmt/ > glusterd.so(__glusterd_peer_rpc_notify+0x14a) [0x7f7677357c6a] > -->/usr/lib/x86_64-lin...
Failure while upgrading gluster to 3.10.1
2017 Jul 03
2
Failure while upgrading gluster to 3.10.1
...clnt_notify+0x88)[0x7f767c23a4a8] >>>>>>> ))))) 0-management: forced unwinding frame type(GLUSTERD-DUMP) op(DUMP(1)) >>>>>>> called at 2017-05-29 11:04:52.183210 (xid=0x23419) >>>>>>> [2017-05-29 11:04:52.183735] W [glusterd-locks.c:681:glusterd_mgmt_v3_unlock] >>>>>>> (-->/usr/lib/x86_64-linux-gnu/glusterfs/3.7.9/xlator/mgmt/gl >>>>>>> usterd.so(glusterd_big_locked_notify+0x4b) [0x7f767734dffb] >>>>>>> -->/usr/lib/x86_64-linux-gnu/glusterfs/3.7.9/xlator/mgmt/glu >>>>>&gt...
Gluster clients can't see directories that exist or are created within a mounted volume, but can enter them.
2017 Nov 06
2
Gluster clients can't see directories that exist or are created within a mounted volume, but can enter them.
Do the users have permission to see/interact with the directories, in addition to the files? On Mon, Nov 6, 2017 at 1:55 PM, Nithya Balachandran <nbalacha at redhat.com> wrote: > Hi, > > Please provide the gluster volume info. Do you see any errors in the > client mount log file (/var/log/glusterfs/var-lib-mountedgluster.log)? > > > Thanks, > Nithya > > On 6
Failure while upgrading gluster to 3.10.1
2017 Jul 03
0
Failure while upgrading gluster to 3.10.1
...;>>>>> ))))) 0-management: forced unwinding frame type(GLUSTERD-DUMP) op(DUMP(1)) >>>>>>>> called at 2017-05-29 11:04:52.183210 (xid=0x23419) >>>>>>>> [2017-05-29 11:04:52.183735] W >>>>>>>> [glusterd-locks.c:681:glusterd_mgmt_v3_unlock] >>>>>>>> (-->/usr/lib/x86_64-linux-gnu/glusterfs/3.7.9/xlator/mgmt/glusterd.so(glusterd_big_locked_notify+0x4b) >>>>>>>> [0x7f767734dffb] >>>>>>>> -->/usr/lib/x86_64-linux-gnu/glusterfs/3.7.9/xlator/mgmt/glusterd.so(__gl...
Gluster failure due to "0-management: Lock not released for <volumename>"
2017 Jun 21
2
Gluster failure due to "0-management: Lock not released for <volumename>"
...eout = 600 for 192.168.150.53:$ [2017-06-21 16:18:34.456522] I [MSGID: 106004] [glusterd-handler.c:5888:__glusterd_peer_rpc_notify] 0-management: Peer <gfsnode2> (<e1e1caa5-9842-40d8-8492-a82b079879a3>), in state <Peer in Cluste$ [2017-06-21 16:18:34.456619] W [glusterd-locks.c:675:glusterd_mgmt_v3_unlock] (-->/usr/lib/x86_64-linux-gnu/glusterfs/3.10.3/xlator/mgmt/glusterd.so(+0x1f 879) [0x7fee6bc22879] -->/usr/lib/x86_64-l$ [2017-06-21 16:18:34.456638] W [MSGID: 106118] [glusterd-handler.c:5913:__glusterd_peer_rpc_notify] 0-management: Lock not released for teravolume [2017-06-21 16:18:34.4...
Gluster failure due to "0-management: Lock not released for <volumename>"
2017 Jun 22
0
Gluster failure due to "0-management: Lock not released for <volumename>"
...3:$ > > [2017-06-21 16:18:34.456522] I [MSGID: 106004] [glusterd-handler.c:5888:__glusterd_peer_rpc_notify] > 0-management: Peer <gfsnode2> (<e1e1caa5-9842-40d8-8492-a82b079879a3>), > in state <Peer in Cluste$ > > [2017-06-21 16:18:34.456619] W [glusterd-locks.c:675:glusterd_mgmt_v3_unlock] > (-->/usr/lib/x86_64-linux-gnu/glusterfs/3.10.3/xlator/mgmt/glusterd.so(+0x1f879) > [0x7fee6bc22879] -->/usr/lib/x86_64-l$ > > [2017-06-21 16:18:34.456638] W [MSGID: 106118] [glusterd-handler.c:5913:__glusterd_peer_rpc_notify] > 0-management: Lock not released for teravolume...
glusterd-locks.c:572:glusterd_mgmt_v3_lock
2017 Jul 20
2
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...x7f17b5c3448f] ) 0-management: Lock for vm-images-repo held by d9047ecd-26b5-467b-8e91-50f76a0c4d16 [2017-07-19 15:07:43.132019] E [MSGID: 106119] [glusterd-op-sm.c:3782:glusterd_op_ac_lock] 0-management: Unable to acquire lock for vm-images-repo [2017-07-19 15:07:43.133568] W [glusterd-locks.c:686:glusterd_mgmt_v3_unlock] (-->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0x3a00f) [0x7f17b5b9e00f] -->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0x2b712) [0x7f17b5b8f712] -->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0xd082a) [0x7f17b5c3482a] ) 0-management: Lock owner mismatch. Lock...
Gluster failure due to "0-management: Lock not released for <volumename>"
2017 Jun 27
2
Gluster failure due to "0-management: Lock not released for <volumename>"
...16:18:34.456522] I [MSGID: 106004] >> [glusterd-handler.c:5888:__glusterd_peer_rpc_notify] 0-management: Peer >> <gfsnode2> (<e1e1caa5-9842-40d8-8492-a82b079879a3>), in state <Peer in >> Cluste$ >> >> [2017-06-21 16:18:34.456619] W [glusterd-locks.c:675:glusterd_mgmt_v3_unlock] >> (-->/usr/lib/x86_64-linux-gnu/glusterfs/3.10.3/xlator/mgmt/glusterd.so(+0x1f879) >> [0x7fee6bc22879] -->/usr/lib/x86_64-l$ >> >> [2017-06-21 16:18:34.456638] W [MSGID: 106118] >> [glusterd-handler.c:5913:__glusterd_peer_rpc_notify] 0-management: Lock >>...
Healing : No space left on device
2018 May 02
3
Healing : No space left on device
...cluster. It is composed of two data nodes and an arbiter for all my volumes. After having upgraded my bricks to gluster 3.12.9 (Fedora 27), this is what I get : ??? - on node 1, volumes won't start, and glusterd.log shows a lot of : ??? ??? [2018-05-02 09:46:06.267817] W [glusterd-locks.c:843:glusterd_mgmt_v3_unlock] (-->/usr/lib64/glusterfs/3.12.9/xlator/mgmt/glusterd.so(+0x22549) [0x7f0047ae2549] -->/usr/lib64/glusterfs/3.12.9/xlator/mgmt/glusterd.so(+0x2bdf0) [0x7f0047aebdf0] -->/usr/lib64/glusterfs/3.12.9/xlator/mgmt/glusterd.so(+0xd8371) [0x7f0047b98371] ) 0-management: Lock for vol thedude not h...
rpc/glusterd-locks error
2018 Feb 26
0
rpc/glusterd-locks error
...sterd on each node in cluster to update (one at a time). The three xx01 nodes all show the following in glusterd.log: [2018-02-26 14:31:47.330670] E [socket.c:2020:__socket_read_frag] 0-rpc: wrong MSG-TYPE (29386) received from 172.26.30.9:24007 [2018-02-26 14:31:47.330879] W [glusterd-locks.c:843:glusterd_mgmt_v3_unlock] (-->/usr/lib64/glusterfs/3.12.5/xlator/mgmt/glusterd.so(+0x2322a) [0x7f46020e922a] -->/usr/lib64/glusterfs/3.12.5/xlator/mgmt/glusterd.so(+0x2d198) [0x7f46020f3198] -->/usr/lib64/glusterfs/3.12.5/xlator/mgmt/glusterd.so(+0xe4755) [0x7f46021aa755] ) 0-management: Lock for vol ovirtprod_vol...
Gluster failure due to "0-management: Lock not released for <volumename>"
2017 Jun 29
0
Gluster failure due to "0-management: Lock not released for <volumename>"
...eout = 600 for 192.168.150.53:$ [2017-06-21 16:18:34.456522] I [MSGID: 106004] [glusterd-handler.c:5888:__glusterd_peer_rpc_notify] 0-management: Peer <gfsnode2> (<e1e1caa5-9842-40d8-8492-a82b079879a3>), in state <Peer in Cluste$ [2017-06-21 16:18:34.456619] W [glusterd-locks.c:675:glusterd_mgmt_v3_unlock] (-->/usr/lib/x86_64-linux-gnu/glusterfs/3.10.3/xlator/mgmt/glusterd.so(+0x1f879) [0x7fee6bc22879] -->/usr/lib/x86_64-l$ [2017-06-21 16:18:34.456638] W [MSGID: 106118] [glusterd-handler.c:5913:__glusterd_peer_rpc_notify] 0-management: Lock not released for teravolume [2017-06-21 16:18:34.45...
glusterd-locks.c:572:glusterd_mgmt_v3_lock
2017 Jul 20
2
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...held by > d9047ecd-26b5-467b-8e91-50f76a0c4d16 > [2017-07-19 15:07:43.132019] E [MSGID: 106119] > [glusterd-op-sm.c:3782:glusterd_op_ac_lock] 0-management: Unable > to acquire lock for vm-images-repo > [2017-07-19 15:07:43.133568] W > [glusterd-locks.c:686:glusterd_mgmt_v3_unlock] > (-->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0x3a00f) > [0x7f17b5b9e00f] > -->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0x2b712) > [0x7f17b5b8f712] > -->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0xd082a) > [0x7f...
Gluster clients can't see directories that exist or are created within a mounted volume, but can enter them.
2017 Nov 08
2
Gluster clients can't see directories that exist or are created within a mounted volume, but can enter them.
...any errors in the >> client mount log file (/var/log/glusterfs/var-lib-mountedgluster.log)? >> > > > root at int-gluster-01:/var/log/glusterfs # grep 'dev_static' *.log|grep -v > cmd_history > > glusterd.log:[2017-11-05 22:37:06.934787] W [glusterd-locks.c:675:glusterd_mgmt_v3_unlock] > (-->/usr/lib64/glusterfs/3.12.2/xlator/mgmt/glusterd.so(+0x22e5a) > [0x7f5047169e5a] -->/usr/lib64/glusterfs/3.12.2/xlator/mgmt/glusterd.so(+0x2cdc8) > [0x7f5047173dc8] -->/usr/lib64/glusterfs/3.12.2/xlator/mgmt/glusterd.so(+0xe372a) > [0x7f504722a72a] ) 0-management: Lock f...
Gluster failure due to "0-management: Lock not released for <volumename>"
2017 Jun 30
3
Gluster failure due to "0-management: Lock not released for <volumename>"
...gt; [2017-06-21 16:18:34.456522] I [MSGID: 106004] > [glusterd-handler.c:5888:__glusterd_peer_rpc_notify] 0-management: Peer > <gfsnode2> (<e1e1caa5-9842-40d8-8492-a82b079879a3>), in state <Peer in > Cluste$ > > [2017-06-21 16:18:34.456619] W > [glusterd-locks.c:675:glusterd_mgmt_v3_unlock] > (-->/usr/lib/x86_64-linux-gnu/glusterfs/3.10.3/xlator/mgmt/glusterd.so(+0x1f879) > [0x7fee6bc22879] -->/usr/lib/x86_64-l$ > > [2017-06-21 16:18:34.456638] W [MSGID: 106118] > [glusterd-handler.c:5913:__glusterd_peer_rpc_notify] 0-management: Lock not > released for teravo...
glusterd-locks.c:572:glusterd_mgmt_v3_lock
2017 Jul 20
2
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...1-50f76a0c4d16 >> [2017-07-19 15:07:43.132019] E [MSGID: 106119] >> [glusterd-op-sm.c:3782:glusterd_op_ac_lock] 0-management: >> Unable to acquire lock for vm-images-repo >> [2017-07-19 15:07:43.133568] W >> [glusterd-locks.c:686:glusterd_mgmt_v3_unlock] >> (-->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0x3a00f) >> [0x7f17b5b9e00f] >> -->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0x2b712) >> [0x7f17b5b8f712] >> -->/usr/lib64/glusterfs/3.8.12/xlator/m...
glusterd-locks.c:572:glusterd_mgmt_v3_lock
2017 Jul 20
0
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...anagement: Lock for vm-images-repo held by > d9047ecd-26b5-467b-8e91-50f76a0c4d16 > [2017-07-19 15:07:43.132019] E [MSGID: 106119] [glusterd-op-sm.c:3782:glusterd_op_ac_lock] > 0-management: Unable to acquire lock for vm-images-repo > [2017-07-19 15:07:43.133568] W [glusterd-locks.c:686:glusterd_mgmt_v3_unlock] > (-->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0x3a00f) > [0x7f17b5b9e00f] -->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0x2b712) > [0x7f17b5b8f712] -->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0xd082a) > [0x7f17b5c3482a] ) 0-management: Lock o...
glusterd-locks.c:572:glusterd_mgmt_v3_lock
2017 Jul 20
0
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...ages-repo held by >> d9047ecd-26b5-467b-8e91-50f76a0c4d16 >> [2017-07-19 15:07:43.132019] E [MSGID: 106119] >> [glusterd-op-sm.c:3782:glusterd_op_ac_lock] 0-management: Unable to >> acquire lock for vm-images-repo >> [2017-07-19 15:07:43.133568] W [glusterd-locks.c:686:glusterd_mgmt_v3_unlock] >> (-->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0x3a00f) >> [0x7f17b5b9e00f] -->/usr/lib64/glusterfs/3.8.12 >> /xlator/mgmt/glusterd.so(+0x2b712) [0x7f17b5b8f712] >> -->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0xd082a) >> [0x7f17b5c348...
glusterd-locks.c:572:glusterd_mgmt_v3_lock
2017 Jul 26
2
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...t;>> d9047ecd-26b5-467b-8e91-50f76a0c4d16 >>> [2017-07-19 15:07:43.132019] E [MSGID: 106119] >>> [glusterd-op-sm.c:3782:glusterd_op_ac_lock] 0-management: Unable to >>> acquire lock for vm-images-repo >>> [2017-07-19 15:07:43.133568] W [glusterd-locks.c:686:glusterd_mgmt_v3_unlock] >>> (-->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0x3a00f) >>> [0x7f17b5b9e00f] -->/usr/lib64/glusterfs/3.8.12 >>> /xlator/mgmt/glusterd.so(+0x2b712) [0x7f17b5b8f712] >>> -->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0xd082a) >&g...
glusterd-locks.c:572:glusterd_mgmt_v3_lock
2017 Jul 26
0
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...gt;> [2017-07-19 15:07:43.132019] E [MSGID: 106119] >>> [glusterd-op-sm.c:3782:glusterd_op_ac_lock] 0-management: >>> Unable to acquire lock for vm-images-repo >>> [2017-07-19 15:07:43.133568] W >>> [glusterd-locks.c:686:glusterd_mgmt_v3_unlock] >>> (-->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0x3a00f) >>> [0x7f17b5b9e00f] >>> -->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0x2b712) >>> [0x7f17b5b8f712] >>> -->/usr/lib64/glust...