From owner-freebsd-stable@FreeBSD.ORG Thu Jun 30 13:47:35 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E30816A41C for ; Thu, 30 Jun 2005 13:47:35 +0000 (GMT) (envelope-from jmartin37@speakeasy.net) Received: from mail27.sea5.speakeasy.net (mail27.sea5.speakeasy.net [69.17.117.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 55DD743D4C for ; Thu, 30 Jun 2005 13:47:35 +0000 (GMT) (envelope-from jmartin37@speakeasy.net) Received: (qmail 9227 invoked from network); 30 Jun 2005 13:47:34 -0000 Received: from adsl-211-141-250.asm.bellsouth.net (HELO [192.168.2.101]) (moonlightcheese@[68.211.141.250]) (envelope-sender ) by mail27.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 30 Jun 2005 13:47:34 -0000 Message-ID: <42C3F7F3.809@speakeasy.net> Date: Thu, 30 Jun 2005 09:47:31 -0400 From: JM User-Agent: Mozilla Thunderbird 1.0.2-1.3.3 (X11/20050513) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brian Fundakowski Feldman References: <200506291704.50185.ndenev@icdsoft.com> <059901c57cb4$9a366220$7f06000a@int.mediasurface.com> <20050630060612.GF1074@green.homeunix.org> In-Reply-To: <20050630060612.GF1074@green.homeunix.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Niki Denev , Steven Hartland , freebsd-stable@freebsd.org Subject: Re: background fsck can be dangerous! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2005 13:47:35 -0000 Brian Fundakowski Feldman wrote: >On Wed, Jun 29, 2005 at 03:12:37PM +0100, Steven Hartland wrote: > > >>I've not had a single crash / power outage that background fsck has >>been able to deal with. 90% of the time the machine will fail to even >>boot to single user mode :( >> >> > >You should turn write caching off on your drives. > > and in addition to that... you can enable a foreground fsck at boot which might be the better option if boot times aren't an issue. > > >> Steve >>----- Original Message ----- >>From: "Niki Denev" >> >> >> >>>I want just to share my last experience with the combination of >>>power failure + background fsck. After the power returned and the >>>machine booted, it sheduled background fsck after 60 seconds, but >>>at this point most of the services were already started, and some of them >>>seemed to rely on files that were probably in unclean state before the >>>check. >>>This unfortunately leaded to some lost email...after the fsck completed, >>>everything runs ok, but i have now set background_fsck to NO in rc.conf. >>> >>>Here is a sad sample from my qmail log file : >>>@4000000042c1badc24fc21cc delivery 1: >>>success: >>>/libexec/ld-elf.so.1:_Shared_object_"libpq.so.3"_not_found,_required_by_"dspam"/did_0+0+1/ >>>@4000000042c1badc24fff25c status: local 2/30 remote 0/20 >>>@4000000042c1badc250151ec delivery 4: >>>success: >>>/libexec/ld-elf.so.1:_Shared_object_"libpq.so.3"_not_found,_required_by_"dspam"/did_0+0+1/ >>>@4000000042c1badc2502bd34 status: local 1/30 remote 0/20 >>>@4000000042c1badc25050ef4 end msg 23982 >>>@4000000042c1badc2508b0a4 delivery 2: >>>success: >>>/libexec/ld-elf.so.1:_Shared_object_"libpq.so.3"_not_found,_required_by_"dspam"/did_0+0+1/ >>>@4000000042c1badc250a9cd4 status: local 0/30 remote 0/20 >>>@4000000042c1badc250c7d4c end msg 24087 >>>@4000000042c1badc2510942c end msg 24040 >>> >>> > >The filesystem looks the same before, during, and after background >fsck runs, other than the free space information. > > >