Date: Sun, 12 Apr 2020 13:20:22 +0000 (UTC) From: Chris Ross <cross+freebsd@distal.com> To: Eugene Grosbein <eugen@grosbein.net> Cc: freebsd-stable@freebsd.org Subject: Re: ZFS server has gone crazy slow Message-ID: <1B88FA01-D6F5-43BC-9351-9076079DC62D@distal.com> In-Reply-To: <89932f19-6aac-5b45-646a-04ceecaaa19d@grosbein.net> References: <2182C27C-A5D3-41BF-9CE9-7C6883E43074@distal.com> <68328a40-0e3d-f9cf-510b-9cbfd7cb8acd@grosbein.net> <654D00F8-DBEC-49BD-B871-7EB830F49D50@distal.com> <89932f19-6aac-5b45-646a-04ceecaaa19d@grosbein.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Apr 12, 2020, at 01:48, Eugene Grosbein <eugen@grosbein.net> wrote: >=20 > There is very simple way to prevent such problem, use: zfs set reservatio= n=3D1G > for single "root" file system of the pool. >=20 > This way ZFS won't allow applications to fill the pool to the point it st= arts crawling. > Instead, writing applications would obtain ENOSPC error when pool's free = space hits the limit. Done. Thank you for that good advice! In case this system develops the same issue in another year or three and I=E2=80=99ve forgotten this, it wil= l yell at me before getting so logged down. - Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1B88FA01-D6F5-43BC-9351-9076079DC62D>