From owner-freebsd-stable@FreeBSD.ORG Wed Jul 29 07:45:28 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7FA0D10656F4 for ; Wed, 29 Jul 2009 07:45:28 +0000 (UTC) (envelope-from cptsalek@gmail.com) Received: from mail-ew0-f213.google.com (mail-ew0-f213.google.com [209.85.219.213]) by mx1.freebsd.org (Postfix) with ESMTP id 0E0AD8FC27 for ; Wed, 29 Jul 2009 07:45:27 +0000 (UTC) (envelope-from cptsalek@gmail.com) Received: by ewy9 with SMTP id 9so478619ewy.43 for ; Wed, 29 Jul 2009 00:45:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=Ge5Qxcna9T5I4yFDAzEqqSo0UuA24fbydSryPZIZx1g=; b=Cpyww+nRIIRjPOvCm/EmoQHYcSrv0U7VI/Yy4jA8YBZpQzh/WxTgMplqMPvCHvA1JK dqc69MRkVa94azO3vERcHNPjnul4MskZWrdQww0H5f/q8JLSc30iBY86qBYOuC/ge6sc vFlzloc3c2Lf04+BQOuuOvqeO4hS/oyQlP2yc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=YrkrLEcFH1KSf16WbDLCwXw72loo3U5WPDTUAVbtb9KXNJ6z50w5yYupssfURJQO6W F3yl9qVFPlQsogcGWlTXGBH7IqmErAdkNhvBvaeKwhBzKDuIHizf8fxvSrnOWDFOKbTi +fWkzBqOYXBcbPT7GpCDVFXSwsWvGLMn0QOMc= MIME-Version: 1.0 Received: by 10.210.63.18 with SMTP id l18mr7803317eba.71.1248853527043; Wed, 29 Jul 2009 00:45:27 -0700 (PDT) In-Reply-To: References: Date: Wed, 29 Jul 2009 09:45:27 +0200 Message-ID: <14989d6e0907290045j94bab06wb5d0114fe2af2331@mail.gmail.com> From: Christian Walther To: FreeBSD Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: Cannot rm files when ZFS is full X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jul 2009 07:45:29 -0000 2009/7/29 grarpamp : > One week old build... > > # df -i . > Filesystem =A0 1K-blocks =A0 =A0 =A0Used Avail Capacity iused ifree %iuse= d =A0Mounted on > ram01/mnt1 239465344 239465344 =A0 =A0 0 =A0 100% =A0 13163 =A0 =A0 0 =A0= 100% =A0 /mnt1 > # ls -aliT zero > 20797 -rw-r--r-- =A01 user user =A043515904 Jul 28 23:20:57 2009 zero > # rm -f zero > rm: zero: No space left on device > # :> zero > cannot create zero: File exists > # cp /dev/null zero > overwrite zero? (y/n [n]) y > # ls -aliT zero > 20797 -rw-rw-rw- =A01 root =A0wheel =A00 Jul 28 23:25:17 2009 zero > # rm -f zero > [gone] this is a known problem with the current version of ZFS. Due to the way ZFS handles access to the data it stores, even a rm causes a write, which requires some additional disk space in the beginning: Instead of simply unlinking what should be removed ZFS creates another tree without the removed data. Only if this new tree has been entirely written to disk the old information is removed. This is a rather rough explanation and probably not entirely correct, but I hope it suffices. Only hope: Make sure that not all disk space is used. Christian