search for: 113001

...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-12-01 14:10:16.862985] I [MSGID: 115063] [server-rpc-fops.c:1317:server_ftruncate_cbk] > 0-c_glusterfs-server: 92: FTRUNCATE 1 (934f08b7-e3b5-4690-84f...

...18] >> [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-12-01 14:10:16.862985] I [MSGID: 115063] >> [server-rpc-fops.c:1317:server_ftruncate_cbk] 0-c_glusterfs-server: 92: >> FTRUNCATE...

....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-12-01 14:10:16.862985] I [MSGID: 115063] >>> [server-rpc-fops.c:1317:server_ftruncate_cbk] 0-c_glusterfs-server: 92: &gt...

...e_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-12-01 14:10:16.862985] I [MSGID: 115063] >>>> [server-rpc-fops.c:1317:server_ftruncate_cbk] 0-c_glusterfs...

...[MSGID: 113027] [posix.c:1538:posix_mkdir] 0-mvol1-posix: mkdir of /brick1/mvol1/.trashcan failed [File exists] [2017-06-23 17:48:30.093701] E [MSGID: 113027] [posix.c:1538:posix_mkdir] 0-mvol1-posix: mkdir of /brick1/mvol1/.trashcan/ failed [File exists] [2017-06-23 17:48:30.113559] E [MSGID: 113001] [posix.c:1562:posix_mkdir] 0-mvol1-posix: setting xattrs on /brick1/mvol1/.trashcan//2290 failed [No such file or directory] [2017-06-23 17:48:30.113630] E [MSGID: 113027] [posix.c:1538:posix_mkdir] 0-mvol1-posix: mkdir of /brick1/mvol1/.trashcan//2290 failed [File exists] [2017-06-23 17:48:30...

...c:1538:posix_mkdir] 0-mvol1-posix: mkdir of? > /brick1/mvol1/.trashcan failed [File exists] > [2017-06-23 17:48:30.093701] E [MSGID: 113027]? > [posix.c:1538:posix_mkdir] 0-mvol1-posix: mkdir of? > /brick1/mvol1/.trashcan/ failed [File exists] > [2017-06-23 17:48:30.113559] E [MSGID: 113001]? > [posix.c:1562:posix_mkdir] 0-mvol1-posix: setting xattrs on? > /brick1/mvol1/.trashcan//2290 failed [No such file or directory] > [2017-06-23 17:48:30.113630] E [MSGID: 113027]? > [posix.c:1538:posix_mkdir] 0-mvol1-posix: mkdir of? > /brick1/mvol1/.trashcan//2290 failed [File exi...

...r] 0-mvol1-posix: mkdir of >> /brick1/mvol1/.trashcan failed [File exists] >> [2017-06-23 17:48:30.093701] E [MSGID: 113027] >> [posix.c:1538:posix_mkdir] 0-mvol1-posix: mkdir of >> /brick1/mvol1/.trashcan/ failed [File exists] >> [2017-06-23 17:48:30.113559] E [MSGID: 113001] >> [posix.c:1562:posix_mkdir] 0-mvol1-posix: setting xattrs on >> /brick1/mvol1/.trashcan//2290 failed [No such file or directory] >> [2017-06-23 17:48:30.113630] E [MSGID: 113027] >> [posix.c:1538:posix_mkdir] 0-mvol1-posix: mkdir of >> /brick1/mvol1/.trashcan//2290...

...arted to spread and this might help. The output of ?gluster volume rebalance $myvolume status? doesn't list any errors so far and the numbers look like realistic values. But we're seeing some strange errors (every few minutes) reports in the journald: ?[2018-04-23 12:31:24.942377] E [MSGID: 113001] [posix.c:5983:_posix_handle_xattr_keyvalue_pair] 0-$myvolume-posix: setxattr failed on /srv/glusterfs/bricks/DATA112/data/.glusterfs/e6/a8/e6a8ce50-fda5-4bad-8d4d-acd25dafcaa2 while doing xattrop: key=trusted.glusterfs.quota.1ce02d3b-b7ae-4485-903c-2991de5350b6.contri.1 [No such file or directory]...

...might > help. The output of ?gluster volume rebalance $myvolume status? doesn't > list any errors so far and the numbers look like realistic values. > But we're seeing some strange errors (every few minutes) reports in the > journald: > ?[2018-04-23 12:31:24.942377] E [MSGID: 113001] > [posix.c:5983:_posix_handle_xattr_keyvalue_pair] 0-$myvolume-posix: > setxattr failed > on /srv/glusterfs/bricks/DATA112/data/.glusterfs/e6/a8/ > e6a8ce50-fda5-4bad-8d4d-acd25dafcaa2 while doing xattrop: > key=trusted.glusterfs.quota.1ce02d3b-b7ae-4485-903c-2991de5350b6.contri.1 &...

...might > help. The output of ?gluster volume rebalance $myvolume status? doesn't > list any errors so far and the numbers look like realistic values. > But we're seeing some strange errors (every few minutes) reports in the > journald: > ?[2018-04-23 12:31:24.942377] E [MSGID: 113001] > [posix.c:5983:_posix_handle_xattr_keyvalue_pair] 0-$myvolume-posix: > setxattr failed > on /srv/glusterfs/bricks/DATA112/data/.glusterfs/e6/a8/ > e6a8ce50-fda5-4bad-8d4d-acd25dafcaa2 while doing xattrop: > key=trusted.glusterfs.quota.1ce02d3b-b7ae-4485-903c-2991de5350b6.contri.1 &...