Date: Mon, 21 Jan 2008 23:43:37 +0100 From: Thomas Vogt <freebsdlists@bsdunix.ch> To: "Julian H. Stacey" <jhs@berklix.org> Cc: freebsd-current@freebsd.org Subject: Re: Can't delete any files on my filled up ZFS pool Message-ID: <47952019.3010309@bsdunix.ch> In-Reply-To: <200801212224.m0LMOoP7072911@fire.js.berklix.net> References: <479515FF.1010709@bsdunix.ch> <200801212224.m0LMOoP7072911@fire.js.berklix.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47952019.3010309>