From owner-freebsd-fs@FreeBSD.ORG Sat Nov 10 23:06:25 2012 Return-Path: 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 830DCA76 for ; Sat, 10 Nov 2012 23:06:25 +0000 (UTC) (envelope-from prvs=1661e47a27=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 0DAFD8FC13 for ; Sat, 10 Nov 2012 23:06:24 +0000 (UTC) Received: from r2d2 ([188.220.16.49]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50001015282.msg for ; Sat, 10 Nov 2012 23:06:15 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Sat, 10 Nov 2012 23:06:15 +0000 (not processed: message from valid local sender) X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=1661e47a27=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-fs@freebsd.org Message-ID: From: "Steven Hartland" To: "Garrett Cooper" , "Mateusz Guzik" References: <509E79C7.10300@shatow.net> <509EA942.9060801@shatow.net> <20121110194759.GA19081@dft-labs.eu> <20121110210317.GC19081@dft-labs.eu> Subject: Re: ZFS can't delete files when over quota Date: Sat, 10 Nov 2012 23:06:21 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Nov 2012 23:06:25 -0000 ----- Original Message ----- From: "Garrett Cooper" >> Except this is not about being unable to rm because of EDQUOT (whether >> ZFS can do something about that or not I have no idea). This is about being >> able to remove just after truncation, which clearly shows that zfs can in >> principle remove this file on its own. >> > > You're probably right. My guess is that the fix would be to ignore > EDQUOT in the unlink VOP handler. The CoW nature of ZFS causes this issue, which is why UFS doesn't have this problem. Unfortunately given ZFS's snapshots there's no guarantee that truncating the file will result in enough free space to perform the unlink. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk.