Received: from maia.hub.org (maia-2.hub.org [200.46.204.251])
	by mail.postgresql.org (Postfix) with ESMTP id 692FE1337B2F
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Wed,  6 Apr 2011 19:59:31 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia,
	port 10024) with ESMTP id 97200-07
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Wed,  6 Apr 2011 22:59:11 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from mx4.wp.pl (mx4.wp.pl [212.77.101.8])
	by mail.postgresql.org (Postfix) with ESMTP id 406501337A5D
	for <pgsql-performance@postgresql.org>;
	Wed,  6 Apr 2011 19:59:09 -0300 (ADT)
Received: (wp-smtpd smtp.wp.pl 22674 invoked from network);
	7 Apr 2011 00:59:09 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wp.pl; s=1024a;
	t=1302130749; bh=mHBqbjwrANJ7htzy8Auj16dS4GTGb0AAEdZZJ2ETBA8=;
	h=From:To:CC:Subject;
	b=bf+QACjGS3VfXrocV/v0P+nxU+Tw1/jzmYhFq2O/q7U6FHyFVMHDvpBvggy1aXvW7
	1tBU7eFWOLjuLf2DGsbe0OVVlQm/o7XcIBwxRX8gNLpmX5k8bClnVlZ5pIF+MiXrTn
	pA0SsZ6Pd8iXd44KyDb+R7Buo6MrEYXA0Tgh/guA=
Received: from aayr148.neoplus.adsl.tpnet.pl (HELO [10.0.0.101])
	(ipluta@[83.6.129.148]) (envelope-sender <ipluta@wp.pl>)
	by smtp.wp.pl (WP-SMTPD) with AES256-SHA encrypted SMTP
	for <scott.marlowe@gmail.com>; 7 Apr 2011 00:59:09 +0200
Message-ID: <4D9CF03C.1020808@wp.pl>
Date: Thu, 07 Apr 2011 00:59:08 +0200
From: Ireneusz Pluta <ipluta@wp.pl>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; pl;
	rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: Scott Marlowe <scott.marlowe@gmail.com>
CC: pgsql-performance@postgresql.org
Subject: Re: Background fsck
References: <4D9CEA3F.5050603@wp.pl>
	<BANLkTim3SY4-P1xzxxfjB9BpvARfWd-Awg@mail.gmail.com>
In-Reply-To: <BANLkTim3SY4-P1xzxxfjB9BpvARfWd-Awg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-WP-AV: skaner antywirusowy poczty Wirtualnej Polski S. A.
X-WP-SPAM: NO 0000000 [wTMU]                               
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.909 tagged_above=-10 required=5
	tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201104/55
X-Sequence-Number: 43117

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?
>
it's ufs2 with softupdates in my case. That's why I am asking abot background fsck.