search for: xlator

.../etc/glusterfs/glusterfs-cli /mnt/glusterfs the log say me: --------- 2008-10-31 12:30:17 D [glusterfs.c:167:get_spec_fp] glusterfs: loading spec from /etc/glusterfs/glusterfs-client.vol 2008-10-31 12:30:17 D [spec.y:107:new_section] parser: New node for 'sirius00' 2008-10-31 12:30:17 D [xlator.c:115:xlator_set_type] xlator: attempt to load file /usr/local/lib/glusterfs/1.3.12/xlator/protocol/client.so 2008-10-31 12:30:17 D [spec.y:127:section_type] parser: Type:sirius00:protocol/client 2008-10-31 12:30:17 D [spec.y:141:section_option] parser: Option:sirius00:transport-type:tcp/client 200...

...on /mnt/vol type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072) Thanks in advace, -Jon Setup info CentOS Linux release 7.4.1708 (Core) 4 GCE Instances (2 US, 2 Asia) 1 10gb Brick/Instance replica 4 volume Packages: glusterfs-client-xlators-3.12.1-2.el7.x86_64 glusterfs-cli-3.12.1-2.el7.x86_64 python2-gluster-3.12.1-2.el7.x86_64 glusterfs-3.12.1-2.el7.x86_64 glusterfs-api-3.12.1-2.el7.x86_64 glusterfs-fuse-3.12.1-2.el7.x86_64 glusterfs-server-3.12.1-2.el7.x86_64 glusterfs-libs-3.12.1-2.el7.x86_64 glusterfs-geo-replication-3.1...

...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-management: Lock for gfs_vms held by a410159b-12db-4cf7...

...lla but did not see anything that looked similar. I just wanted to check that I was not hitting some know issue and/or doing something stupid, before I open a bug. This is from the brick log: [2017-06-28 17:38:43.565378] E [posix.c:3327:_fill_writev_xdata] > (-->/usr/lib64/glusterfs/3.10.2/xlator/features/trash.so(+0x2bd3) > [0x7ff81964ebd3] > -->/usr/lib64/glusterfs/3.10.2/xlator/storage/posix.so(+0x1e546) > [0x7ff819e96546] > -->/usr/lib64/glusterfs/3.10.2/xlator/storage/posix.so(+0x1e2ff) > [0x7ff819e962ff] > ) 0-homes-posix: fd: 0x7ff7b4121bf0 inode: > 0x7ff7b...

...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-management: Lock for gfs_vms held by a410159b-12db-4cf7...

...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-management: Lock for gfs_vms held by a410159b-12db-4cf7...

...:~# > > 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-management: Lock for gfs_vms held by a410159b-12db-4cf7...

...gt; 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-management: Lock for gfs_vms h...

...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-management: Lock for gfs_vms h...

...n 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-management...

...2 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 held by 2c6f154f-efe3-4479-addc-b2021aa9d5df...

...up_id=0,default_permissions,allow_other,max_read=131072) > > > Thanks in advace, > -Jon > > > Setup info > CentOS Linux release 7.4.1708 (Core) > 4 GCE Instances (2 US, 2 Asia) > 1 10gb Brick/Instance > replica 4 volume > > Packages: > > glusterfs-client-xlators-3.12.1-2.el7.x86_64 > glusterfs-cli-3.12.1-2.el7.x86_64 > python2-gluster-3.12.1-2.el7.x86_64 > glusterfs-3.12.1-2.el7.x86_64 > glusterfs-api-3.12.1-2.el7.x86_64 > glusterfs-fuse-3.12.1-2.el7.x86_64 > glusterfs-server-3.12.1-2.el7.x86_64 > glusterfs-libs-3.12.1-2.el7.x86_64 &g...

...e > > 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-manag...

...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...

...0 Reading symbols from /lib/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.6 Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /usr/local/lib/glusterfs/3.0.4/xlator/protocol/client.so...done. Loaded symbols for /usr/local/lib/glusterfs/3.0.4/xlator/protocol/client.so Reading symbols from /usr/local/lib/glusterfs/3.0.4/xlator/performance/write-behind.so...done. Loaded symbols for /usr/local/lib/glusterfs/3.0.4/xlator/performance/write-behind.so Reading symbol...

...lusterd-proc-mgmt.c:83:glusterd_proc_stop] 0-management: scrub already stopped [2017-06-16 16:08:14.412451] I [MSGID: 106568] [glusterd-svc-mgmt.c:228:glusterd_svc_stop] 0-management: scrub service is stopped [2017-06-16 16:08:14.437968] I [run.c:191:runner_log] (-->/usr/lib64/glusterfs/3.10.1/xlator/mgmt/glusterd.so(+0xdb46a) [0x7f30460bc46a] -->/usr/lib64/glusterfs/3.10.1/xlator/mgmt/glusterd.so(+0xdaf2d) [0x7f30460bbf2d] -->/lib64/libglusterfs.so.0(runner_log+0x115) [0x7f3051532255] ) 0-management: Ran script: /var/lib/glusterd/hooks/1/set/post/S30samba-set.sh --volname=intermediate01...

...ol.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]...

...t 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 held by > 2c6f154f-efe3-447...

...d () from /lib64/libpthread.so.0 #4 0x0000003d998e8bbd in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f413aa48700 (LWP 104255)): #0 0x0000003d99c0b68c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f413befb99b in hooks_worker () from /usr/lib64/glusterfs/3.10.5/xlator/mgmt/glusterd.so #2 0x0000003d99c07aa1 in start_thread () from /lib64/libpthread.so.0 #3 0x0000003d998e8bbd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f413a047700 (LWP 104256)): #0 0x00007f41462fd43d in dict_lookup_common () from /usr/lib64/libglusterfs.so.0 #1 0x00007f41462ff33d in...

....0 > #4 0x0000003d998e8bbd in clone () from /lib64/libc.so.6 > Thread 3 (Thread 0x7f413aa48700 (LWP 104255)): > #0 0x0000003d99c0b68c in pthread_cond_wait@@GLIBC_2.3.2 () from > /lib64/libpthread.so.0 > #1 0x00007f413befb99b in hooks_worker () from > /usr/lib64/glusterfs/3.10.5/xlator/mgmt/glusterd.so > #2 0x0000003d99c07aa1 in start_thread () from /lib64/libpthread.so.0 > #3 0x0000003d998e8bbd in clone () from /lib64/libc.so.6 > Thread 2 (Thread 0x7f413a047700 (LWP 104256)): > #0 0x00007f41462fd43d in dict_lookup_common () from > /usr/lib64/libglusterfs.so.0 &...