Btw after few more seconds in SIGTERM scenario, VM kind of revived and seems to be fine... And after few more restarts of fio job, I got I/O error. -ps On Fri, Sep 8, 2017 at 2:11 PM, Pavel Szalbot <pavel.szalbot@xxxxxxxxx> wrote: > Gandalf, SIGKILL (killall -9 glusterfsd) did not stop I/O after few > minutes. SIGTERM on the other hand causes crash, but this time it is > not read-only remount, but around 10 IOPS tops and 2 IOPS on average. > -ps > > > On Fri, Sep 8, 2017 at 1:56 PM, Diego Remolina <dijuremo@xxxxxxxxx> wrote: >> I currently only have a Windows 2012 R2 server VM in testing on top of >> the gluster storage, so I will have to take some time to provision a >> couple Linux VMs with both ext4 and XFS to see what happens on those. >> >> The Windows server VM is OK with killall glusterfsd, but when the 42 >> second timeout goes into effect, it gets paused and I have to go into >> RHEVM to un-pause it. >> >> Diego >> >> On Fri, Sep 8, 2017 at 7:53 AM, Gandalf Corvotempesta >> <gandalf.corvotempesta@xxxxxxxxx> wrote: >>> 2017-09-08 13:44 GMT+02:00 Pavel Szalbot <pavel.szalbot@xxxxxxxxx>: >>>> I did not test SIGKILL because I suppose if graceful exit is bad, SIGKILL >>>> will be as well. This assumption might be wrong. So I will test it. It would >>>> be interesting to see client to work in case of crash (SIGKILL) and not in >>>> case of graceful exit of glusterfsd. >>> >>> Exactly. if this happen, probably there is a bug in gluster's signal management. _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users
