Re: Can't delete any files on my filled up ZFS pool

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_at_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 _at_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_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to 
> "freebsd-current-unsubscribe_at_freebsd.org"
>