search for: c_glusterfs

Displaying 7 results from an estimated 7 matches for "c_glusterfs".

2017 Dec 06
1
Crash in glusterd!!!
...i Team, > > We are getting the crash in glusterd after start of it. When I tried to > debug in brick logs we are getting below errors: > > [2017-12-01 14:10:14.684122] E [MSGID: 100018] > [glusterfsd.c:1960:glusterfs_pidfile_update] 0-glusterfsd: pidfile > /system/glusterd/vols/c_glusterfs/run/10.32.1.144-opt-lvmdir-c2-brick.pid > lock failed [Resource temporarily unavailable] > : > : > : > [2017-12-01 14:10:16.862903] E [MSGID: 113001] [posix-helpers.c:1228:posix_fhandle_pair] > 0-c_glusterfs-posix: fd=18: key:trusted.bit-rot.version [No space left on > device]...
2017 Dec 06
2
[Gluster-devel] Crash in glusterd!!!
...are getting the crash in glusterd after start of it. When I tried to >> debug in brick logs we are getting below errors: >> >> [2017-12-01 14:10:14.684122] E [MSGID: 100018] >> [glusterfsd.c:1960:glusterfs_pidfile_update] 0-glusterfsd: pidfile >> /system/glusterd/vols/c_glusterfs/run/10.32.1.144-opt-lvmdir-c2-brick.pid >> lock failed [Resource temporarily unavailable] >> : >> : >> : >> [2017-12-01 14:10:16.862903] E [MSGID: 113001] >> [posix-helpers.c:1228:posix_fhandle_pair] 0-c_glusterfs-posix: fd=18: >> key:trusted.bit-rot.versio...
2017 Dec 06
0
[Gluster-devel] Crash in glusterd!!!
...sh in glusterd after start of it. When I tried to >>> debug in brick logs we are getting below errors: >>> >>> [2017-12-01 14:10:14.684122] E [MSGID: 100018] >>> [glusterfsd.c:1960:glusterfs_pidfile_update] 0-glusterfsd: pidfile >>> /system/glusterd/vols/c_glusterfs/run/10.32.1.144-opt-lvmdir-c2-brick.pid >>> lock failed [Resource temporarily unavailable] >>> : >>> : >>> : >>> [2017-12-01 14:10:16.862903] E [MSGID: 113001] >>> [posix-helpers.c:1228:posix_fhandle_pair] 0-c_glusterfs-posix: fd=18: >>&gt...
2017 Dec 06
1
[Gluster-devel] Crash in glusterd!!!
...start of it. When I tried to >>>> debug in brick logs we are getting below errors: >>>> >>>> [2017-12-01 14:10:14.684122] E [MSGID: 100018] >>>> [glusterfsd.c:1960:glusterfs_pidfile_update] 0-glusterfsd: pidfile >>>> /system/glusterd/vols/c_glusterfs/run/10.32.1.144-opt-lvmdir-c2-brick.pid >>>> lock failed [Resource temporarily unavailable] >>>> : >>>> : >>>> : >>>> [2017-12-01 14:10:16.862903] E [MSGID: 113001] >>>> [posix-helpers.c:1228:posix_fhandle_pair] 0-c_glusterfs-p...
2017 May 09
1
Empty info file preventing glusterd from starting
...on: 30706 [2017-05-06 03:33:39.827515] E [MSGID: 106206] [glusterd-store.c:2562:glusterd_store_update_volinfo] 0-management: Failed to get next store iter [2017-05-06 03:33:39.827563] E [MSGID: 106207] [glusterd-store.c:2844:glusterd_store_retrieve_volume] 0-management: Failed to update volinfo for c_glusterfs volume [2017-05-06 03:33:39.827625] E [MSGID: 106201] [glusterd-store.c:3042:glusterd_store_retrieve_volumes] 0-management: Unable to restore volume: c_glusterfs [2017-05-06 03:33:39.827722] E [MSGID: 101019] [xlator.c:428:xlator_init] 0-management: Initialization of volume 'management' fai...
2017 Jun 01
2
[Gluster-devel] Empty info file preventing glusterd from starting
...ed to get next store iter > > >>>>>>>> [2017-05-06 03:33:39.827563] E [MSGID: 106207] > > >>>>>>>> [glusterd-store.c:2844:glusterd_store_retrieve_volume] > > >>>>>>>> 0-management: Failed to update volinfo for c_glusterfs volume > > >>>>>>>> [2017-05-06 03:33:39.827625] E [MSGID: 106201] > > >>>>>>>> [glusterd-store.c:3042:glusterd_store_retrieve_volumes] > > >>>>>>>> 0-management: Unable to restore volume: c_glusterfs > &gt...
2017 Jun 01
0
[Gluster-devel] Empty info file preventing glusterd from starting
...store iter > > > >>>>>>>> [2017-05-06 03:33:39.827563] E [MSGID: 106207] > > > >>>>>>>> [glusterd-store.c:2844:glusterd_store_retrieve_volume] > > > >>>>>>>> 0-management: Failed to update volinfo for c_glusterfs volume > > > >>>>>>>> [2017-05-06 03:33:39.827625] E [MSGID: 106201] > > > >>>>>>>> [glusterd-store.c:3042:glusterd_store_retrieve_volumes] > > > >>>>>>>> 0-management: Unable to restore volume: c_glu...