Date: Fri, 13 Jul 2018 15:22:39 -0400 From: Mike Tancsa <mike@sentex.net> To: Jim Long <list@museum.rain.com> Cc: freebsd-questions@freebsd.org Subject: Re: Disk/ZFS activity crash on 11.2-STABLE [SOLVED] Message-ID: <ebcb9d30-59be-bcb8-ecaf-cce316d999eb@sentex.net> In-Reply-To: <20180713191050.GA98371@g5.umpquanet.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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 :) If you ever have a system with a LOT of small files and directories, a handy value to tune / keep an eye on is the mix allocated to metadata vs file data. vfs.zfs.arc_meta_limit. You can tell when doing things like "ls" in a directory takes a LONG time to list files. In my case, I had many directories with 50,000+ files. Also things like 'zfs list -t snapshot' start to take a long time. ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 x203 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ebcb9d30-59be-bcb8-ecaf-cce316d999eb>