Re: Background fsck - Mailing list pgsql-performance

From Scott Marlowe
Subject Re: Background fsck
Date
Msg-id BANLkTim3SY4-P1xzxxfjB9BpvARfWd-Awg@mail.gmail.com
Whole thread Raw
In response to Background fsck  (Ireneusz Pluta <ipluta@wp.pl>)
Responses Re: Background fsck  (Ireneusz Pluta <ipluta@wp.pl>)
Re: Background fsck  (Ivan Voras <ivoras@freebsd.org>)
List pgsql-performance
On Wed, Apr 6, 2011 at 4:33 PM, Ireneusz Pluta <ipluta@wp.pl> wrote:
> Hello,
>
> I saw some recommendations from people on the net not to use background fsck
> when running PostgreSQL on FreeBSD. As I recall, these opinions were just
> thoughts of people which they shared with the community, following their bad
> experience caused by using background fsck. So, not coming any deeper with
> underatanding why not, I use that as a clear recommendation for myself and
> keep background fsck turned off on all my machines, regardless how much
> faster a server could come up after a crash.
>
> But waiting so much time (like now) during foreground fsck of a large data
> filesystem after unclean shutdown, makes me to come to this group to ask
> whether I really need to avoid background fsck on a PostgreSQL machine?
> Could I hear your opinions?

Shouldn't a journaling file system just come back up almost immediately?

pgsql-performance by date:

Previous
From: Ireneusz Pluta
Date:
Subject: Background fsck
Next
From: Ireneusz Pluta
Date:
Subject: Re: Background fsck