From owner-freebsd-questions@freebsd.org Thu Jul 9 17:18:06 2015 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9484F9979D9 for ; Thu, 9 Jul 2015 17:18:06 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: from mail-qg0-f44.google.com (mail-qg0-f44.google.com [209.85.192.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 544D41C48 for ; Thu, 9 Jul 2015 17:18:05 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: by qgef3 with SMTP id f3so68350965qge.0 for ; Thu, 09 Jul 2015 10:17:59 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:content-transfer-encoding:message-id:references:to; bh=QQYVRMUiN+wQ+WhLhPTgW/b79qXjXKJ2gNGzP+mDhsk=; b=kEWyym+nhcjxdHZMNTs5RH4rYX0wXULJl0JbIsNVUd+/oiIVJaEobem/XmNr89tHjX UVC3PdcSa3vf9pvHczsmn76qB1hgYi+TGcjco+NZfgR37vJAe1gMJKhVBOMsFgv8arsT RQEyZwq8wnjq83c9vM+LbwptD97ZDbuB0PnUpg7ej7nG8MWmVNL53rEtApenmOE0BW0I /uQAHQNrmvntQOCyX6hS+atYIs0a2uDsinJMrpG/mMZTmGSNIAjYFpxyin+naxblYnXr an9SVb1jsXoPgChcFomdKVStpCitk4v/SLYX3K5T1Ooy8F86o5toqlF7pt/bpS4VDylE aqwg== X-Gm-Message-State: ALoCoQmfu1IbRebU+3pNurDrhuzSAUoXq9vO5hrHDPoNehx1GWMnbnwAc8hYMUHRP6fnLsDyRnno X-Received: by 10.55.54.65 with SMTP id d62mr26266769qka.59.1436461940373; Thu, 09 Jul 2015 10:12:20 -0700 (PDT) Received: from mbp-1.thecreativeadvantage.com (mail.thecreativeadvantage.com. [96.236.20.34]) by smtp.gmail.com with ESMTPSA id 60sm4007756qgy.11.2015.07.09.10.12.18 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 09 Jul 2015 10:12:19 -0700 (PDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: Gmirror/graid or hardware raid? From: Paul Kraus In-Reply-To: <559EA804.9030501@sneakertech.com> Date: Thu, 9 Jul 2015 13:12:19 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <83187224-AE6F-4C57-890C-F53077A1C5F4@kraus-haus.org> References: <917A821C-02F8-4F96-88DA-071E3431C335@mac.com> <7F08761C-556E-4147-95DB-E84B4E5179A5@kraus-haus.org> <559EA804.9030501@sneakertech.com> To: FreeBSD - X-Mailer: Apple Mail (2.1878.6) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jul 2015 17:18:06 -0000 On Jul 9, 2015, at 12:57, Quartz 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 = 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