Date: Thu, 9 Jul 2015 13:12:19 -0400 From: Paul Kraus <paul@kraus-haus.org> To: FreeBSD - <freebsd-questions@freebsd.org> Subject: Re: Gmirror/graid or hardware raid? Message-ID: <83187224-AE6F-4C57-890C-F53077A1C5F4@kraus-haus.org> In-Reply-To: <559EA804.9030501@sneakertech.com> References: <CA%2ByoEx-T5V3Rchxugke3%2BoUno6SwXHW1%2Bx466kWtb8VNYb%2BBbg@mail.gmail.com> <917A821C-02F8-4F96-88DA-071E3431C335@mac.com> <7F08761C-556E-4147-95DB-E84B4E5179A5@kraus-haus.org> <559EA804.9030501@sneakertech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jul 9, 2015, at 12:57, Quartz <quartz@sneakertech.com> wrote: >> I also create a =93do-not-remove=94 dataset in every zpool with 1 GB >> reserved and quota. ZFS behaves very, very badly when FULL. This give >> me a cushion when things go badly so I can delete whatever used up >> all the space =85 Yes, ZFS cannot delete files if the FS is = completely >> FULL. I leave the =93do-not-remove=94 dataset unmounted so that it = cannot >> be used. >=20 > Wouldn't it be easier just to set a quota on the root dataset? Setting a quota will not work as it will limit all the child datasets as = well. You could set a refquota, if you were not using the root dataset = for anything (which is the default behavior of FBSD when installed ZFS = only). I started doing this on servers before we had the ref<n> = parameters and old habits die hard :-) In general, the =93ref=94 version of dataset parameters was a great = addition so that you could see what a point in the _middle_ of a = hierarchy was doing and control it. -- Paul Kraus paul@kraus-haus.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?83187224-AE6F-4C57-890C-F53077A1C5F4>