From owner-freebsd-current@FreeBSD.ORG Mon Jan 21 22:22:51 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 CFD5216A421 for ; Mon, 21 Jan 2008 22:22:51 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.freebsd.org (Postfix) with ESMTP id 59C8713C474 for ; Mon, 21 Jan 2008 22:22:50 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from js.berklix.net (p549A4A80.dip.t-dialin.net [84.154.74.128]) (authenticated bits=0) by tower.berklix.org (8.13.6/8.13.6) with ESMTP id m0LMMgBP054836; Mon, 21 Jan 2008 22:22:47 GMT (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by js.berklix.net (8.13.8/8.13.8) with ESMTP id m0LMP1H6060213; Mon, 21 Jan 2008 23:25:02 +0100 (CET) (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.13.8/8.13.8) with ESMTP id m0LMOoP7072911; Mon, 21 Jan 2008 23:24:55 +0100 (CET) (envelope-from jhs@fire.js.berklix.net) Message-Id: <200801212224.m0LMOoP7072911@fire.js.berklix.net> To: Thomas Vogt In-reply-to: <479515FF.1010709@bsdunix.ch> References: <479515FF.1010709@bsdunix.ch> Comments: In-reply-to Thomas Vogt message dated "Mon, 21 Jan 2008 23:00:31 +0100." Date: Mon, 21 Jan 2008 23:24:50 +0100 From: "Julian H. Stacey" Cc: 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 22:22:51 -0000 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. Or B) Perhaps more likely: truncate existing inode to create some space before deleting it: cat /dev/null > input.wav ; rm input.wav 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. -- Julian Stacey. Munich Computer Consultant, BSD Unix C Linux. http://berklix.com