[Bugs] [Bug 1633318] New: health check fails on restart from crash

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1633318

            Bug ID: 1633318
           Summary: health check fails on restart from crash
           Product: GlusterFS
           Version: 4.1
         Component: posix
          Assignee: bugs at gluster.org
          Reporter: joe at julianfamily.org
                CC: bugs at gluster.org



Description of problem:
If a brick process exits without cleaning up .glusterfs/health_check, the next
start causes the health check to fail - apparently because the health_check
file exists.

Version-Release number of selected component (if applicable):
4.1.2

How reproducible:
always

Steps to Reproduce:
1. pkill -9 -f glusterfs
2. systemctl start glusterd

Actual results:
[2018-09-26 16:04:14.154211] W [MSGID: 113117]
[posix-metadata.c:671:posix_set_parent_ctime] 0-vminstances-posix: posix parent
set mdata failed on file [File exists]
[2018-09-26 16:04:14.262538] W [MSGID: 113117]
[posix-metadata.c:671:posix_set_parent_ctime] 0-vminstances-posix: posix parent
set mdata failed on file [Invalid argument]
[2018-09-26 16:04:20.169870] W [MSGID: 113075]
[posix-helpers.c:1895:posix_fs_health_check] 0-vminstances-posix:
aio_read_cmp_buf() on /data/gluster/instances/brick/.glusterfs/health_check
returned
[2018-09-26 16:04:20.169993] M [MSGID: 113075]
[posix-helpers.c:1962:posix_health_check_thread_proc] 0-vminstances-posix:
health-check failed, going down
[2018-09-26 16:04:20.186505] M [MSGID: 113075]
[posix-helpers.c:1981:posix_health_check_thread_proc] 0-vminstances-posix:
still alive! -> SIGTERM


Expected results:
health check succeeds

Additional info:

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.