search for: glusterd_mgmt_v3_lock

Displaying 17 results from an estimated 17 matches for "glusterd_mgmt_v3_lock".

Using glusterfs for virtual machines with qcow2 images
2023 Jun 01
3
Using glusterfs for virtual machines with qcow2 images
...k gluster3.linova.de:/glusterfs/sde1enc/brick Status: Connected Number of entries: 0 root at gluster1:~# This are the warnings and errors I've found in the logs on our three servers... * Warnings on gluster1.linova.de: glusterd.log:[2023-05-31 23:56:00.032233 +0000] W [glusterd-locks.c:545:glusterd_mgmt_v3_lock] (-->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0x26edf) [0x7f9b8d19eedf] -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0xcdad2) [0x7f9b8d245ad2] -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0xcc525) [0x7f9b8d244525] ) 0...
Using glusterfs for virtual machines with qcow2 images
2023 Jun 07
1
Using glusterfs for virtual machines with qcow2 images
...k gluster3.linova.de:/glusterfs/sde1enc/brick Status: Connected Number of entries: 0 root at gluster1:~# This are the warnings and errors I've found in the logs on our three servers... * Warnings on gluster1.linova.de: glusterd.log:[2023-05-31 23:56:00.032233 +0000] W [glusterd-locks.c:545:glusterd_mgmt_v3_lock] (-->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0x26edf) [0x7f9b8d19eedf] -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0xcdad2) [0x7f9b8d245ad2] -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0xcc525) [0x7f9b8d244525] ) 0...
Using glusterfs for virtual machines with qcow2 images
2023 Jun 01
1
Using glusterfs for virtual machines with qcow2 images
...ck gluster3.linova.de:/glusterfs/sde1enc/brick Status: Connected Number of entries: 0 root at gluster1:~# This are the warnings and errors I've found in the logs on our three servers... * Warnings on gluster1.linova.de: glusterd.log:[2023-05-31 23:56:00.032233 +0000] W [glusterd-locks.c:545:glusterd_mgmt_v3_lock] (-->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0x26edf) [0x7f9b8d19eedf] -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0xcdad2) [0x7f9b8d245ad2] -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0xcc525) [0x7f9b8d244525] ) 0...
[EXT] [Glusterusers] Using glusterfs for virtual machines with qco
2023 Jun 01
1
[EXT] [Glusterusers] Using glusterfs for virtual machines with qco
...Status: Connected > Number of entries: 0 > > root at gluster1:~# > > This are the warnings and errors I've found in the logs on our three > servers... > > * Warnings on gluster1.linova.de: > > glusterd.log:[2023-05-31 23:56:00.032233 +0000] W [glusterd-locks.c:545:glusterd_mgmt_v3_lock] (-->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0x26edf) [0x7f9b8d19eedf] -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0xcdad2) [0x7f9b8d245ad2] -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0xcc525) [0x7f9b8d244525] ) 0...
Using glusterfs for virtual machines with qcow2 images
2023 Jun 07
1
Using glusterfs for virtual machines with qcow2 images
...us: Connected > Number of entries: 0 > > root at gluster1:~# > > This are the warnings and errors I've found in the logs on our three > servers... > > * Warnings on gluster1.linova.de: > > glusterd.log:[2023-05-31 23:56:00.032233 +0000] W > [glusterd-locks.c:545:glusterd_mgmt_v3_lock] > (-->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0x26edf) > [0x7f9b8d19eedf] > -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0xcdad2) > [0x7f9b8d245ad2] > -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0xcc...
[EXT] [Glusterusers] Using glusterfs for virtual machines with qco
2023 Jun 02
1
[EXT] [Glusterusers] Using glusterfs for virtual machines with qco
...> > > root at gluster1:~# > > > > This are the warnings and errors I've found in the logs on our three > > servers... > > > > * Warnings on gluster1.linova.de: > > > > glusterd.log:[2023-05-31 23:56:00.032233 +0000] W > [glusterd-locks.c:545:glusterd_mgmt_v3_lock] > (-->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0x26edf) > [0x7f9b8d19eedf] > -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0xcdad2) > [0x7f9b8d245ad2] > -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0xcc...
[EXT] [Glusterusers] Using glusterfs for virtual machines with qco
2023 Jun 02
1
[EXT] [Glusterusers] Using glusterfs for virtual machines with qco
...~# >> > >> > This are the warnings and errors I've found in the logs on our three >> > servers... >> > >> > * Warnings on gluster1.linova.de: >> > >> > glusterd.log:[2023-05-31 23:56:00.032233 +0000] W >> [glusterd-locks.c:545:glusterd_mgmt_v3_lock] >> (-->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0x26edf) >> [0x7f9b8d19eedf] >> -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0xcdad2) >> [0x7f9b8d245ad2] >> -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mg...
glusterd-locks.c:572:glusterd_mgmt_v3_lock
2018 Mar 15
0
glusterd-locks.c:572:glusterd_mgmt_v3_lock
Hi, have you found a solution? Regards, -- Marco Crociani
glusterd-locks.c:572:glusterd_mgmt_v3_lock
2017 Jul 20
0
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...t; I'm using gluster 3.8.12 on CentOS 7.3, the only relevant information that > I found on the log file (etc-glusterfs-glusterd.vol.log) of my three > nodes are the following: > > * node1, at the moment the issue begins: > > [2017-07-19 15:07:43.130203] W [glusterd-locks.c:572:glusterd_mgmt_v3_lock] > (-->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0x3a00f) > [0x7f373f25f00f] -->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0x2ba25) > [0x7f373f250a25] -->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0xd048f) > [0x7f373f2f548f] ) 0-management: Lock f...
[EXT] [Glusterusers] Using glusterfs for virtual machines with qco
2023 Jun 05
1
[EXT] [Glusterusers] Using glusterfs for virtual machines with qco
...> This are the warnings and errors I've found in the logs on our three > > servers... > > > > * Warnings on gluster1.linova.de: > > > > glusterd.log:[2023-05-31 23:56:00.032233 +0000] W > [glusterd-locks.c:545:glusterd_mgmt_v3_lock] (-->/usr/lib/ > x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0x26edf) > [0x7f9b8d19eedf] -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/ > mgmt/glusterd.so(+0xcdad2) [0x7f9b8d245ad2] -->/usr/lib/ > x86_64-linux-gnu/glusterfs/10.1/xla...
glusterd-locks.c:572:glusterd_mgmt_v3_lock
2017 Jul 20
2
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...thing is working as expected. I'm using gluster 3.8.12 on CentOS 7.3, the only relevant information that I found on the log file (etc-glusterfs-glusterd.vol.log) of my three nodes are the following: * node1, at the moment the issue begins: [2017-07-19 15:07:43.130203] W [glusterd-locks.c:572:glusterd_mgmt_v3_lock] (-->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0x3a00f) [0x7f373f25f00f] -->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0x2ba25) [0x7f373f250a25] -->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0xd048f) [0x7f373f2f548f] ) 0-management: Lock for vm-images-repo he...
glusterd-locks.c:572:glusterd_mgmt_v3_lock
2017 Jul 20
0
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...3.8.12 on CentOS 7.3, the only relevant information >> that I found on the log file (etc-glusterfs-glusterd.vol.log) of my >> three nodes are the following: >> >> * node1, at the moment the issue begins: >> >> [2017-07-19 15:07:43.130203] W [glusterd-locks.c:572:glusterd_mgmt_v3_lock] >> (-->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0x3a00f) >> [0x7f373f25f00f] -->/usr/lib64/glusterfs/3.8.12 >> /xlator/mgmt/glusterd.so(+0x2ba25) [0x7f373f250a25] >> -->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0xd048f) >> [0x7f373f2f54...
glusterd-locks.c:572:glusterd_mgmt_v3_lock
2017 Jul 20
2
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...3.8.12 on CentOS 7.3, the only relevant > information that I found on the log file > (etc-glusterfs-glusterd.vol.log) of my three nodes are the following: > > * node1, at the moment the issue begins: > > [2017-07-19 15:07:43.130203] W > [glusterd-locks.c:572:glusterd_mgmt_v3_lock] > (-->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0x3a00f) > [0x7f373f25f00f] > -->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0x2ba25) > [0x7f373f250a25] > -->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0xd048f) > [0x7f...
glusterd-locks.c:572:glusterd_mgmt_v3_lock
2017 Jul 26
0
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...file >>> (etc-glusterfs-glusterd.vol.log) of my three nodes are the >>> following: >>> >>> * node1, at the moment the issue begins: >>> >>> [2017-07-19 15:07:43.130203] W >>> [glusterd-locks.c:572:glusterd_mgmt_v3_lock] >>> (-->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0x3a00f) >>> [0x7f373f25f00f] >>> -->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0x2ba25) >>> [0x7f373f250a25] >>> -->/usr/lib64/glust...
glusterd-locks.c:572:glusterd_mgmt_v3_lock
2017 Jul 20
2
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...ion that I found on the log file >> (etc-glusterfs-glusterd.vol.log) of my three nodes are the >> following: >> >> * node1, at the moment the issue begins: >> >> [2017-07-19 15:07:43.130203] W >> [glusterd-locks.c:572:glusterd_mgmt_v3_lock] >> (-->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0x3a00f) >> [0x7f373f25f00f] >> -->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0x2ba25) >> [0x7f373f250a25] >> -->/usr/lib64/glusterfs/3.8.12/xlator/m...
glusterd-locks.c:572:glusterd_mgmt_v3_lock
2017 Jul 27
0
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...-glusterd.vol.log) of my three nodes are >>>> the following: >>>> >>>> * node1, at the moment the issue begins: >>>> >>>> [2017-07-19 15:07:43.130203] W >>>> [glusterd-locks.c:572:glusterd_mgmt_v3_lock] >>>> (-->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0x3a00f) >>>> [0x7f373f25f00f] >>>> -->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0x2ba25) >>>> [0x7f373f250a25] >>&gt...
glusterd-locks.c:572:glusterd_mgmt_v3_lock
2017 Jul 26
2
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...he only relevant information >>> that I found on the log file (etc-glusterfs-glusterd.vol.log) of my >>> three nodes are the following: >>> >>> * node1, at the moment the issue begins: >>> >>> [2017-07-19 15:07:43.130203] W [glusterd-locks.c:572:glusterd_mgmt_v3_lock] >>> (-->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0x3a00f) >>> [0x7f373f25f00f] -->/usr/lib64/glusterfs/3.8.12 >>> /xlator/mgmt/glusterd.so(+0x2ba25) [0x7f373f250a25] >>> -->/usr/lib64/glusterfs/3.8.12/xlator/mgmt/glusterd.so(+0xd048f) >&g...