Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 26 Oct 2010 12:02:20 +0200
From:      Erik Stian Tefre <erik@tefre.com>
To:        Giulio Ferro <auryn@zirakzigil.org>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: ZFS wrong size stats with amavis
Message-ID:  <4CC6A72C.80406@tefre.com>
In-Reply-To: <4CC18BB9.2030200@zirakzigil.org>
References:  <4CC18BB9.2030200@zirakzigil.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 10/22/10 15:03, Giulio Ferro wrote:
> I've seen people discuss about this and it happened to me as well.
> 
> Freebsd 8.1 stable 25th september amd64
> This server has one single boot disk with ufs + 1 array (hardware, 3ware)
> which hold 2,7TB data. I've formatted the latter with ZFS.
> 
> Things seemed to work ok until I upgraded the system. One day the server
> jails didn't boot anymore. I checked and the array occupation was 100% with
> 0 byte free.
> 
> This sounded strange, so I found a hidden file under
> /var/amavis/.spamassassin.
> I removed the dir, started again, but after a while it grew again until
> the system became unusable.
> 
> This is how I solved: I moved the amavis partition under UFS, then
> mounted with nullfs that dir under /var in the zfs jail.
> 
> I solved in the sense that it didn't grow anymore, but the fs occupation
> stayed very near 100%, with only 1GB free space.
> 
> If I launch du -s under /zfs (host machine, not jail) I get a total space
> of about 750GB, but df -h always turns up with 2,7TB space occupied.
> 
> I tried a zpool upgrade zfs and zpool scrub zfs, but to no avail.
> 
> What should I do. short of moving the data, destroying the pool and
> creating it again (which I can't very easily do)?

I had the same problem with extremely large files in
/var/amavis/.spamassassin after upgrading from 7.x to 8.1 (zpool mirror,
no compression, zpool upgraded to v14, zfs filesystems upgraded to v3).

This worked for me as a fix/workaround:
zfs create pool/newamavisjail
rm /pool/oldamavisjail/var/amavis/.spamassassin/[hugefiles]
rsync ... /pool/oldamavisjail /pool/newamavisjail
portsnap fetch update; portupgrade -af (in newamavisjail)
restart newamavisjail

I don't think I permanently lost disk space from the pool because of
this. I guess you have checked that there are no snapshots referring to
the huge files? (zfs list and zfs list -t snapshot)

--
Erik



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4CC6A72C.80406>