From owner-freebsd-fs@FreeBSD.ORG  Sat Nov 10 23:59:14 2012
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
 by hub.freebsd.org (Postfix) with ESMTP id C7923ED6
 for <freebsd-fs@freebsd.org>; Sat, 10 Nov 2012 23:59:14 +0000 (UTC)
 (envelope-from grarpamp@gmail.com)
Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com
 [209.85.214.182])
 by mx1.freebsd.org (Postfix) with ESMTP id 8B0848FC08
 for <freebsd-fs@freebsd.org>; Sat, 10 Nov 2012 23:59:14 +0000 (UTC)
Received: by mail-ob0-f182.google.com with SMTP id wc20so6519338obb.13
 for <freebsd-fs@freebsd.org>; Sat, 10 Nov 2012 15:59:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=Fjans/yCU0S4Or0oBMY1Qlqlulzz4JY6sxax5tbGUWY=;
 b=WBOm14jyNNpgz/y9VTZbksbhlUpREMpgSmgAm2usThXwLVCO7yDjYIcCyEve/lvXnB
 tXni9rFSrJXJAHNXtQLHeSrlCybji4p0LQR8r0DyKmsSLeExVKij1mN6xg7ZNOCZTz+N
 m6NQama20vkqLo0EqVh2qDrm0G15oRGjAUKCuP+f0W3f/bkAmnnoe6lyZnI9Lg7EAfvX
 59COTH0VgHkxY5RkIwriApZli3AtaKs9P47bs0GhMB2X6aC1ErkHrXpm8rkHusZKlLAp
 GyFJck8dMNjPPPiyU3TBoJW5NhuKMxg4DycTHV6oCMgnz1q/XZIEYZ/Ll7p/aF59S+jC
 akDA==
MIME-Version: 1.0
Received: by 10.60.11.68 with SMTP id o4mr8772043oeb.89.1352591948319; Sat, 10
 Nov 2012 15:59:08 -0800 (PST)
Received: by 10.76.68.39 with HTTP; Sat, 10 Nov 2012 15:59:08 -0800 (PST)
Date: Sat, 10 Nov 2012 18:59:08 -0500
Message-ID: <CAD2Ti2_LTa1kydDH1eUNTG5es3gdU6GdU=uSwdcr0n7MqRVjYA@mail.gmail.com>
Subject: ZFS can't delete files when over quota
From: grarpamp <grarpamp@gmail.com>
To: freebsd-fs@freebsd.org
Content-Type: text/plain; charset=UTF-8
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Nov 2012 23:59:14 -0000

NAME                     USED  AVAIL  REFER  MOUNTPOINT
tank/distfiles          10.0G      0    25K  /tank/distfiles
NAME            PROPERTY               VALUE
tank/distfiles  quota                  10G

What is your free in 'zpool list tank'?
Because of CoW for metadata, I think it makes sense that
your tank/distfiles won't rm within your used up 10G limit there.
What if you raise the distfiles limit to use more of tank?
What if you rollback distfiles?
And consider using per user/group quotas so root can still
rm in tank/distfiles [1].

[1] Sure, ZFS arguably should make internal reserved
space to allow rm (the effective metadata). Question is,
how much, what dynamic metrics for that? Maybe ZFS
feel admin still has some responsibility. But you really
don't want to take a user ticket because they can't
manage their own rm as under other file systems.
What is the state of this in current Solaris?