pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: pgsql-performance@postgresql.org
Subject: Re: On Linux Filesystems
Date: Tue, 12 Aug 2003 09:36:21 -0700
Message-ID: <200308120936.21099.josh@agliodbs.com> (raw)
In-Reply-To: <20030812142856.GB12701@libertyrms.info>
References: <20030810200440.B2396@cookie>
	<m34r0nh99x.fsf_-_@chvatal.cbbrowne.com>
	<20030812142856.GB12701@libertyrms.info>

People:

> On Mon, Aug 11, 2003 at 10:58:18PM -0400, Christopher Browne wrote:
> > 1.  Nobody has gone through any formal proofs, and there are few
> > systems _anywhere_ that are 100% reliable.
>
> I think the problem is that ext2 is known to be not perfectly crash
> safe.  That is, fsck on reboot after a crash can cause, in some
> extreme cases, recently-fscynced data to end up in lost+found/.  The
> data may or may not be recoverable from there.

Aside from that, as recently as eighteen months ago I had to manually fsck an 
ext2 system after an unexpected power-out.   After my interactive session the 
system recovered and no data was lost.  However, the client lost 3.5 hours of 
work time ... 2.5 hours for me to get to the site, and 1 hour to recover the 
server (mostly waiting time).  

So it's a tradeoff with loss of performance vs. recovery time.   In a server 
room with redundant backup power supplies, "clean room" security and 
fail-over services, I can certainly imagine that data journalling would not 
be needed.   That is, however, the minority ...

-- 
Josh Berkus
Aglio Database Solutions
San Francisco



view thread (8+ messages)  latest in thread

Message-ID: <200308120936.21099.josh@agliodbs.com>
Permalink:  ../200308120936.21099.josh@agliodbs.com/
Also on:    postgresql.org/message-id/200308120936.21099.josh@agliodbs.com

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: josh@agliodbs.com
  Subject: Re: On Linux Filesystems
  In-Reply-To: <200308120936.21099.josh@agliodbs.com>
  References: <20030810200440.B2396@cookie> <m34r0nh99x.fsf_-_@chvatal.cbbrowne.com> <20030812142856.GB12701@libertyrms.info> <200308120936.21099.josh@agliodbs.com>

* 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