Date: Sat, 14 Jul 2018 15:11:21 +0930 From: Shane Ambler <FreeBSD@ShaneWare.Biz> To: Mike Tancsa <mike@sentex.net>, Jim Long <list@museum.rain.com> Cc: freebsd-questions@freebsd.org Subject: Re: Disk/ZFS activity crash on 11.2-STABLE [SOLVED] Message-ID: <4d4726a7-66e0-4f7e-f230-b68e440ad8f6@ShaneWare.Biz> In-Reply-To: <ebcb9d30-59be-bcb8-ecaf-cce316d999eb@sentex.net> References: <20180711212959.GA81029@g5.umpquanet.com> <5ebd8573-1363-06c7-cbb2-8298b0894319@sentex.net> <20180712183512.GA75020@g5.umpquanet.com> <a069a076-df1c-80b2-1116-787e0a948ed9@sentex.net> <20180712214248.GA98578@g5.umpquanet.com> <20180713191050.GA98371@g5.umpquanet.com> <ebcb9d30-59be-bcb8-ecaf-cce316d999eb@sentex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 14/07/2018 04:52, Mike Tancsa wrote: > On 7/13/2018 3:10 PM, Jim Long wrote: >> >> It appears that limiting the ARC size did it. The 'zfs send -R' was >> able to complete with ARC limited to 50G, and a second run with a 60G >> ARC limit also completed. > > Great! I am glad that helped. Its helpful to me too as I have some > systems I am upgrading to RELENG_11 from RELENG_10 soon. I was aware of > this particular issue, but was worried perhaps your crashes were related > to something else I might run into :) To add my 2c - I recently realised that the arc_max defaults allow all ram to be allocated as wired, which is bad. arc_max should not be set higher than physical ram - max_wired - buffer It is time I put this into a bug report - https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229764 -- FreeBSD - the place to B...Storing Data Shane Ambler
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4d4726a7-66e0-4f7e-f230-b68e440ad8f6>