search for: gd_sync_task_begin

Displaying 20 results from an estimated 20 matches for "gd_sync_task_begin".

Using glusterfs for virtual machines with qcow2 images
2023 Jun 01
3
Using glusterfs for virtual machines with qcow2 images
...->/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-bad5-c5c817679d1b * Errors on gluster1.linova.de: glusterd.log:[2023-05-31 23:56:00.032251 +0000] E [MSGID: 106118] [glusterd-syncop.c:1904:gd_sync_task_begin] 0-management: Unable to acquire lock for gfs_vms glusterd.log:[2023-06-01 02:22:04.133274 +0000] E [MSGID: 106118] [glusterd-syncop.c:1904:gd_sync_task_begin] 0-management: Unable to acquire lock for gfs_vms glusterd.log:[2023-06-01 02:44:00.046099 +0000] E [MSGID: 106118] [glusterd-syncop.c:190...
Using glusterfs for virtual machines with qcow2 images
2023 Jun 07
1
Using glusterfs for virtual machines with qcow2 images
...->/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-bad5-c5c817679d1b * Errors on gluster1.linova.de: glusterd.log:[2023-05-31 23:56:00.032251 +0000] E [MSGID: 106118] [glusterd-syncop.c:1904:gd_sync_task_begin] 0-management: Unable to acquire lock for gfs_vms glusterd.log:[2023-06-01 02:22:04.133274 +0000] E [MSGID: 106118] [glusterd-syncop.c:1904:gd_sync_task_begin] 0-management: Unable to acquire lock for gfs_vms glusterd.log:[2023-06-01 02:44:00.046099 +0000] E [MSGID: 106118] [glusterd-syncop.c:190...
Using glusterfs for virtual machines with qcow2 images
2023 Jun 01
1
Using glusterfs for virtual machines with qcow2 images
...-->/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-bad5-c5c817679d1b * Errors on gluster1.linova.de: glusterd.log:[2023-05-31 23:56:00.032251 +0000] E [MSGID: 106118] [glusterd-syncop.c:1904:gd_sync_task_begin] 0-management: Unable to acquire lock for gfs_vms glusterd.log:[2023-06-01 02:22:04.133274 +0000] E [MSGID: 106118] [glusterd-syncop.c:1904:gd_sync_task_begin] 0-management: Unable to acquire lock for gfs_vms glusterd.log:[2023-06-01 02:44:00.046099 +0000] E [MSGID: 106118] [glusterd-syncop.c:1904:...
[EXT] [Glusterusers] Using glusterfs for virtual machines with qco
2023 Jun 01
1
[EXT] [Glusterusers] Using glusterfs for virtual machines with qco
..._64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0xcc525) [0x7f9b8d244525] ) 0-management: Lock for gfs_vms held by a410159b-12db-4cf7-bad5-c5c817679d1b > > * Errors on gluster1.linova.de: > > glusterd.log:[2023-05-31 23:56:00.032251 +0000] E [MSGID: 106118] [glusterd-syncop.c:1904:gd_sync_task_begin] 0-management: Unable to acquire lock for gfs_vms > glusterd.log:[2023-06-01 02:22:04.133274 +0000] E [MSGID: 106118] [glusterd-syncop.c:1904:gd_sync_task_begin] 0-management: Unable to acquire lock for gfs_vms > glusterd.log:[2023-06-01 02:44:00.046099 +0000] E [MSGID: 106118] [glusterd-sync...
Using glusterfs for virtual machines with qcow2 images
2023 Jun 07
1
Using glusterfs for virtual machines with qcow2 images
...lusterfs/10.1/xlator/mgmt/glusterd.so(+0xcc525) > [0x7f9b8d244525] ) 0-management: Lock for gfs_vms held by > a410159b-12db-4cf7-bad5-c5c817679d1b > > * Errors on gluster1.linova.de: > > glusterd.log:[2023-05-31 23:56:00.032251 +0000] E [MSGID: 106118] > [glusterd-syncop.c:1904:gd_sync_task_begin] 0-management: Unable to acquire > lock for gfs_vms > glusterd.log:[2023-06-01 02:22:04.133274 +0000] E [MSGID: 106118] > [glusterd-syncop.c:1904:gd_sync_task_begin] 0-management: Unable to acquire > lock for gfs_vms > glusterd.log:[2023-06-01 02:44:00.046099 +0000] E [MSGID: 106118]...
[EXT] [Glusterusers] Using glusterfs for virtual machines with qco
2023 Jun 02
1
[EXT] [Glusterusers] Using glusterfs for virtual machines with qco
.../mgmt/glusterd.so(+0xcc525) > [0x7f9b8d244525] ) 0-management: Lock for gfs_vms held by > a410159b-12db-4cf7-bad5-c5c817679d1b > > > > * Errors on gluster1.linova.de: > > > > glusterd.log:[2023-05-31 23:56:00.032251 +0000] E [MSGID: 106118] > [glusterd-syncop.c:1904:gd_sync_task_begin] 0-management: Unable to acquire > lock for gfs_vms > > glusterd.log:[2023-06-01 02:22:04.133274 +0000] E [MSGID: 106118] > [glusterd-syncop.c:1904:gd_sync_task_begin] 0-management: Unable to acquire > lock for gfs_vms > > glusterd.log:[2023-06-01 02:44:00.046099 +0000] E [MSGI...
[EXT] [Glusterusers] Using glusterfs for virtual machines with qco
2023 Jun 02
1
[EXT] [Glusterusers] Using glusterfs for virtual machines with qco
...>> [0x7f9b8d244525] ) 0-management: Lock for gfs_vms held by >> a410159b-12db-4cf7-bad5-c5c817679d1b >> > >> > * Errors on gluster1.linova.de: >> > >> > glusterd.log:[2023-05-31 23:56:00.032251 +0000] E [MSGID: 106118] >> [glusterd-syncop.c:1904:gd_sync_task_begin] 0-management: Unable to acquire >> lock for gfs_vms >> > glusterd.log:[2023-06-01 02:22:04.133274 +0000] E [MSGID: 106118] >> [glusterd-syncop.c:1904:gd_sync_task_begin] 0-management: Unable to acquire >> lock for gfs_vms >> > glusterd.log:[2023-06-01 02:44:00.0...
[EXT] [Glusterusers] Using glusterfs for virtual machines with qco
2023 Jun 05
1
[EXT] [Glusterusers] Using glusterfs for virtual machines with qco
...244525] ) 0-management: Lock for gfs_vms held by > a410159b-12db-4cf7-bad5-c5c817679d1b > > > > * Errors on gluster1.linova.de: > > > > glusterd.log:[2023-05-31 23:56:00.032251 +0000] E [MSGID: 106118] > [glusterd-syncop.c:1904:gd_sync_task_begin] 0-management: Unable to > acquire lock for gfs_vms > > glusterd.log:[2023-06-01 02:22:04.133274 +0000] E [MSGID: 106118] > [glusterd-syncop.c:1904:gd_sync_task_begin] 0-management: Unable to > acquire lock for gfs_vms > > glusterd.log:[2023-0...
not able to restart the brick for distributed volume
2013 Aug 08
2
not able to restart the brick for distributed volume
...:19:42.280852] I [glusterd-pmap.c:271:pmap_registry_remove] 0-pmap: removing brick (null) on port 49160 [2013-08-08 14:19:42.283583] E [glusterd-utils.c:4023:glusterd_brick_start] 0-management: Unable to start brick 192.168.24.80:/.krfs/_home [2013-08-08 14:19:42.283637] E [glusterd-syncop.c:830:gd_sync_task_begin] 0-management: Commit of operation 'Volume Start' failed on localhost and the gluster volume remains as stopped root at ksc-base-unit0:/.krfs> gluster volume info _home Volume Name: _home Type: Distribute Volume ID: e6ab94d8-30ec-469e-830f-4c124e360ca1 Status: Stopped Number of Brick...
glusterd-locks.c:572:glusterd_mgmt_v3_lock
2017 Jul 20
2
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...-gluster. Please check log file for details. [2017-07-19 15:07:43.131293] E [MSGID: 106116] [glusterd-mgmt.c:135:gd_mgmt_v3_collate_errors] 0-management: Locking failed on virtnode-0-2-gluster. Please check log file for details. [2017-07-19 15:07:43.131360] E [MSGID: 106151] [glusterd-syncop.c:1884:gd_sync_task_begin] 0-management: Locking Peers Failed. [2017-07-19 15:07:43.132005] E [MSGID: 106116] [glusterd-mgmt.c:135:gd_mgmt_v3_collate_errors] 0-management: Unlocking failed on virtnode-0-2-gluster. Please check log file for details. [2017-07-19 15:07:43.132182] E [MSGID: 106116] [glusterd-mgmt.c:135:gd_mgmt_...
glusterd-locks.c:572:glusterd_mgmt_v3_lock
2017 Jul 20
2
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...[2017-07-19 15:07:43.131293] E [MSGID: 106116] > [glusterd-mgmt.c:135:gd_mgmt_v3_collate_errors] 0-management: > Locking failed on virtnode-0-2-gluster. Please check log file for > details. > [2017-07-19 15:07:43.131360] E [MSGID: 106151] > [glusterd-syncop.c:1884:gd_sync_task_begin] 0-management: Locking > Peers Failed. > [2017-07-19 15:07:43.132005] E [MSGID: 106116] > [glusterd-mgmt.c:135:gd_mgmt_v3_collate_errors] 0-management: > Unlocking failed on virtnode-0-2-gluster. Please check log file > for details. > [2017-07-19 15:07:43.1...
volume start causes glusterd to core dump in 3.5.0
2014 Apr 28
2
volume start causes glusterd to core dump in 3.5.0
...sterd.so(glusterd_op_start_volume+0xfd)[0x7eff45e45a8d] /usr/lib64/glusterfs/3.5.0/xlator/mgmt/glusterd.so(glusterd_op_commit_perform+0x53b)[0x7eff45df471b] /usr/lib64/glusterfs/3.5.0/xlator/mgmt/glusterd.so(gd_commit_op_phase+0xbe)[0x7eff45e5193e] /usr/lib64/glusterfs/3.5.0/xlator/mgmt/glusterd.so(gd_sync_task_begin+0x2c2)[0x7eff45e53632] /usr/lib64/glusterfs/3.5.0/xlator/mgmt/glusterd.so(glusterd_op_begin_synctask+0x3b)[0x7eff45e5376b] /usr/lib64/glusterfs/3.5.0/xlator/mgmt/glusterd.so(__glusterd_handle_cli_start_volume+0x1b6)[0x7eff45e46cc6] /usr/lib64/glusterfs/3.5.0/xlator/mgmt/glusterd.so(glusterd_big_loc...
glusterd-locks.c:572:glusterd_mgmt_v3_lock
2017 Jul 20
2
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...06116] >> [glusterd-mgmt.c:135:gd_mgmt_v3_collate_errors] 0-management: >> Locking failed on virtnode-0-2-gluster. Please check log file >> for details. >> [2017-07-19 15:07:43.131360] E [MSGID: 106151] >> [glusterd-syncop.c:1884:gd_sync_task_begin] 0-management: >> Locking Peers Failed. >> [2017-07-19 15:07:43.132005] E [MSGID: 106116] >> [glusterd-mgmt.c:135:gd_mgmt_v3_collate_errors] 0-management: >> Unlocking failed on virtnode-0-2-gluster. Please check log >> file for...
glusterd-locks.c:572:glusterd_mgmt_v3_lock
2017 Jul 20
0
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...ck log file for details. > [2017-07-19 15:07:43.131293] E [MSGID: 106116] > [glusterd-mgmt.c:135:gd_mgmt_v3_collate_errors] 0-management: Locking > failed on virtnode-0-2-gluster. Please check log file for details. > [2017-07-19 15:07:43.131360] E [MSGID: 106151] [glusterd-syncop.c:1884:gd_sync_task_begin] > 0-management: Locking Peers Failed. > [2017-07-19 15:07:43.132005] E [MSGID: 106116] > [glusterd-mgmt.c:135:gd_mgmt_v3_collate_errors] 0-management: Unlocking > failed on virtnode-0-2-gluster. Please check log file for details. > [2017-07-19 15:07:43.132182] E [MSGID: 106116] >...
trash can feature, crashed???
2017 Jun 20
2
trash can feature, crashed???
..._storage.sh --volname=intermediate01 -o features.trash=on --gd-workdir=/var/lib/glusterd [2017-06-16 16:08:22.416477] E [MSGID: 106525] [glusterd-op-sm.c:4188:glusterd_dict_set_volid] 0-management: Volume date01 does not exist [2017-06-16 16:08:22.416525] E [MSGID: 106289] [glusterd-syncop.c:1927:gd_sync_task_begin] 0-management: Failed to build payload for operation 'Volume Set' [2017-06-16 16:08:28.452042] I [MSGID: 106568] [glusterd-svc-mgmt.c:228:glusterd_svc_stop] 0-management: bitd service is stopped [2017-06-16 16:08:28.452204] I [MSGID: 106132] [glusterd-proc-mgmt.c:83:glusterd_proc_stop] 0-...
glusterd-locks.c:572:glusterd_mgmt_v3_lock
2017 Jul 20
0
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...>> [2017-07-19 15:07:43.131293] E [MSGID: 106116] >> [glusterd-mgmt.c:135:gd_mgmt_v3_collate_errors] 0-management: Locking >> failed on virtnode-0-2-gluster. Please check log file for details. >> [2017-07-19 15:07:43.131360] E [MSGID: 106151] >> [glusterd-syncop.c:1884:gd_sync_task_begin] 0-management: Locking Peers >> Failed. >> [2017-07-19 15:07:43.132005] E [MSGID: 106116] >> [glusterd-mgmt.c:135:gd_mgmt_v3_collate_errors] 0-management: Unlocking >> failed on virtnode-0-2-gluster. Please check log file for details. >> [2017-07-19 15:07:43.132182] E...
glusterd-locks.c:572:glusterd_mgmt_v3_lock
2017 Jul 26
2
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...7-19 15:07:43.131293] E [MSGID: 106116] >>> [glusterd-mgmt.c:135:gd_mgmt_v3_collate_errors] 0-management: Locking >>> failed on virtnode-0-2-gluster. Please check log file for details. >>> [2017-07-19 15:07:43.131360] E [MSGID: 106151] >>> [glusterd-syncop.c:1884:gd_sync_task_begin] 0-management: Locking Peers >>> Failed. >>> [2017-07-19 15:07:43.132005] E [MSGID: 106116] >>> [glusterd-mgmt.c:135:gd_mgmt_v3_collate_errors] 0-management: Unlocking >>> failed on virtnode-0-2-gluster. Please check log file for details. >>> [2017-07-19...
glusterd-locks.c:572:glusterd_mgmt_v3_lock
2017 Jul 26
0
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...[glusterd-mgmt.c:135:gd_mgmt_v3_collate_errors] >>> 0-management: Locking failed on virtnode-0-2-gluster. Please >>> check log file for details. >>> [2017-07-19 15:07:43.131360] E [MSGID: 106151] >>> [glusterd-syncop.c:1884:gd_sync_task_begin] 0-management: >>> Locking Peers Failed. >>> [2017-07-19 15:07:43.132005] E [MSGID: 106116] >>> [glusterd-mgmt.c:135:gd_mgmt_v3_collate_errors] >>> 0-management: Unlocking failed on virtnode-0-2-gluster. >>> Please...
trash can feature, crashed???
2017 Jun 20
0
trash can feature, crashed???
...tures.trash=on --gd-workdir=/var/lib/glusterd > [2017-06-16 16:08:22.416477] E [MSGID: 106525] [glusterd-op-sm.c:4188:glusterd_dict_set_volid] 0- > management: Volume date01 does not exist See the above log entry ^^ > [2017-06-16 16:08:22.416525] E [MSGID: 106289] [glusterd-syncop.c:1927:gd_sync_task_begin] 0- > management: Failed to build payload for operation 'Volume Set' > [2017-06-16 16:08:28.452042] I [MSGID: 106568] [glusterd-svc-mgmt.c:228:glusterd_svc_stop] 0- > management: bitd service is stopped > [2017-06-16 16:08:28.452204] I [MSGID: 106132] [glusterd-proc-mgmt.c:83:gl...
glusterd-locks.c:572:glusterd_mgmt_v3_lock
2017 Jul 27
0
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...mgmt_v3_collate_errors] >>>> 0-management: Locking failed on virtnode-0-2-gluster. >>>> Please check log file for details. >>>> [2017-07-19 15:07:43.131360] E [MSGID: 106151] >>>> [glusterd-syncop.c:1884:gd_sync_task_begin] >>>> 0-management: Locking Peers Failed. >>>> [2017-07-19 15:07:43.132005] E [MSGID: 106116] >>>> [glusterd-mgmt.c:135:gd_mgmt_v3_collate_errors] >>>> 0-management: Unlocking failed on virtnode-0-2-glus...