Date: Fri, 25 Jan 2019 09:16:33 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 234576] hastd exits ungracefully Message-ID: <bug-234576-227-wMGiXco7ey@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-234576-227@https.bugs.freebsd.org/bugzilla/> References: <bug-234576-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D234576 Paul Thornton <freebsd-bugzilla@prt.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freebsd-bugzilla@prt.org --- Comment #1 from Paul Thornton <freebsd-bugzilla@prt.org> --- I see exactly the same hastd issue on 12.0-RELEASE-p2, with hast directly on top of the drives (no partitions) - I don't think that specifically is your problem. HAST seems to be broken in some other way with 12.0 However, my setup is slightly complicated as I have a zpool using GELI devi= ces, running above HAST. I am currently doing some testing to reduce this to the simplest reproducible setup to remove everything else, and then turn up some debugging. What I've noted so far is: 1) All of the hastd worker threads die virtually simultaneously. 2) This doesn't appear happen immediately you start writing data, but a very short while afterwards (order of a few seconds). As a side note for anyone else reading, I had issues making HAST work relia= bly in my setup under 11 as well, but this was easier to track down and patch. = The high level problem I found there was that ggate_recv received more data than MAXPHYS and the "impossible" condition of ENOMEM happened (line 1264 of primary.c). After adding some logging here, I "fixed" this by setting gctl_length to MAXPHYS + 0x200 in both primary.c and secondary.c which stop= ped the problem; this isn't exactly elegant but it worked OK for me. The issue reported in this bug seems unrelated to that. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-234576-227-wMGiXco7ey>