Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 42D309FB8BA for ; Wed, 16 May 2007 20:29:00 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 77693-07 for ; Wed, 16 May 2007 20:28:50 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from smtp4.clear.net.nz (smtp4.clear.net.nz [203.97.37.64]) by postgresql.org (Postfix) with ESMTP id A1F5D9FA4C2 for ; Wed, 16 May 2007 20:28:54 -0300 (ADT) Received: from [192.168.1.11] (121-72-77-1.dsl.telstraclear.net [121.72.77.1]) by smtp4.clear.net.nz (CLEAR Net Mail) with ESMTP id <0JI5003ORQK3Q330@smtp4.clear.net.nz> for pgsql-performance@postgresql.org; Thu, 17 May 2007 11:28:52 +1200 (NZST) Date: Thu, 17 May 2007 11:28:30 +1200 From: Mark Kirkwood Subject: Re: Disk Fills Up and fsck "Compresses" it In-reply-to: <20070516155145.GM14548@nasby.net> To: "Jim C. Nasby" , Y Sidhu Cc: pgsql-performance@postgresql.org Message-id: <464B939E.8090402@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit References: <20070515234152.GD20707@nasby.net> <20070516155145.GM14548@nasby.net> User-Agent: Thunderbird 1.5.0.10 (X11/20070313) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/296 X-Sequence-Number: 24686 Jim C. Nasby wrote: > No, it's part of FreeBSD's UFS. google FreeBSD softupdates and you > should get plenty of info. > > As I said, it's probably not worth worrying about. > > On Wed, May 16, 2007 at 08:21:23AM -0700, Y Sidhu wrote: >> What do you mean by "softupdates?" Is that a parameter in what I am guessing >> is the conf file? Here is quite a good article on the interaction of fsck and softupdates in FreeBSD: http://www.usenix.org/publications/library/proceedings/bsdcon02/mckusick/mckusick_html/index.html Having said that, it seems to talk about space lost by unreferenced blocks and inodes is the context of panic or power outage, as opposed to normal softupdate operation (unless I'm missing something...) Cheers Mark