From: Mark Kirkwood <markir@paradise.net.nz>
To: Jim C. Nasby <decibel@decibel.org>
To: Y Sidhu <ysidhu@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Disk Fills Up and fsck "Compresses" it
Date: Thu, 17 May 2007 11:28:30 +1200
Message-ID: <464B939E.8090402@paradise.net.nz> (raw)
In-Reply-To: <20070516155145.GM14548@nasby.net>
References: <b09064f30705151318v2c770d76h89e32c9303777070@mail.gmail.com>
<20070515234152.GD20707@nasby.net>
<b09064f30705160821k55a37476v65ba5ab054473cd2@mail.gmail.com>
<20070516155145.GM14548@nasby.net>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: markir@paradise.net.nz, decibel@decibel.org, ysidhu@gmail.com
Subject: Re: Disk Fills Up and fsck "Compresses" it
In-Reply-To: <464B939E.8090402@paradise.net.nz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox