From owner-freebsd-current@FreeBSD.ORG Mon Jan 21 23:20:40 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A272A16A419 for ; Mon, 21 Jan 2008 23:20:40 +0000 (UTC) (envelope-from lists+freebsd-current@xinu.tv) Received: from fugu.xinu.tv (fugu.slackasses.com [204.11.33.69]) by mx1.freebsd.org (Postfix) with ESMTP id 7BF8813C4D3 for ; Mon, 21 Jan 2008 23:20:40 +0000 (UTC) (envelope-from lists+freebsd-current@xinu.tv) Received: from [192.168.3.3] (c-68-40-200-8.hsd1.mi.comcast.net [68.40.200.8]) by fugu.xinu.tv (Postfix) with ESMTP id 288A04A42FF; Mon, 21 Jan 2008 17:57:57 -0500 (EST) Message-ID: <479523CF.7020804@xinu.tv> Date: Mon, 21 Jan 2008 17:59:27 -0500 From: Bill User-Agent: Thunderbird 2.0.0.6 (X11/20071022) MIME-Version: 1.0 To: Thomas Vogt References: <479515FF.1010709@bsdunix.ch> <200801212224.m0LMOoP7072911@fire.js.berklix.net> <47952019.3010309@bsdunix.ch> In-Reply-To: <47952019.3010309@bsdunix.ch> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Julian H. Stacey" , freebsd-current@freebsd.org Subject: Re: Can't delete any files on my filled up ZFS pool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jan 2008 23:20:40 -0000 Do you have snapshots on the pool? What is the output from 'zfs list'? It's possible when you have a snapshot on tank that the delete causes a copy-on-write for the snapshot that then doesn't have enough space. Bill Thomas Vogt wrote: > Hello Julian > > Julian H. Stacey wrote: >> Thomas Vogt wrote: >>> Hello >>> >>> I need help. My ZFS sytem is filled up. I can't delete any files. >>> >>> root@bert:/tank# rm input.wav >>> rm: input.wav: No space left on device >> >> I know nothing about ZFS :-) (Well nearly, just reading the ZFS pain >> on @freebsd lists is enough to scare me off for now ;-) ) But if I >> was stuck on this, with no ZFS experts to quickly ask, I'd guess & try: >> >> It needs more space for another Inode, or extended directory >> entry, cos its maybe going to create another inode in a >> backup/ deleted entity first, so either: >> >> A) >> Maybe su ; rm input.wav # if the concept of extra space still >> exists >> # per "tunefs -m" for root as per UFS etc. > > I filled it as root. So it does not work > >> Or B) >> Perhaps more likely: >> truncate existing inode to create some space >> before deleting it: >> cat /dev/null > input.wav ; rm input.wav > > Nice. B) works fine. Thank you. > > >> Presumably if you filled it as root, B might still empty it. >> >> There will doubtless be better ZFS answers, but could be interesting >> to hear if either of above could work. > > I hope there will be a "ZFS" answer :) > > Regards, > Thomas > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" >