From owner-freebsd-stable@FreeBSD.ORG Wed May 13 20:47:17 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BAAAC1065690 for ; Wed, 13 May 2009 20:47:17 +0000 (UTC) (envelope-from andrew@modulus.org) Received: from email.octopus.com.au (email.octopus.com.au [122.100.2.232]) by mx1.freebsd.org (Postfix) with ESMTP id 7993F8FC15 for ; Wed, 13 May 2009 20:47:16 +0000 (UTC) (envelope-from andrew@modulus.org) Received: by email.octopus.com.au (Postfix, from userid 1002) id F23D517E5D; Thu, 14 May 2009 06:47:34 +1000 (EST) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on email.octopus.com.au X-Spam-Level: X-Spam-Status: No, score=-1.4 required=10.0 tests=ALL_TRUSTED autolearn=failed version=3.2.3 Received: from [10.1.50.60] (ppp121-44-128-236.lns10.syd7.internode.on.net [121.44.128.236]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: admin@email.octopus.com.au) by email.octopus.com.au (Postfix) with ESMTP id BC7ED17D78; Thu, 14 May 2009 06:47:30 +1000 (EST) Message-ID: <4A0B31A2.9030805@modulus.org> Date: Thu, 14 May 2009 06:46:26 +1000 From: Andrew Snow User-Agent: Thunderbird 2.0.0.14 (X11/20080523) MIME-Version: 1.0 To: Pat Wendorf References: <2c2c47aa0905121110i6355930bwce3a9c6afb117d4d@mail.gmail.com> <200905131124.16897.milu@dat.pl> <2c2c47aa0905131337w4a338386t2407f7df7a398cf7@mail.gmail.com> In-Reply-To: <2c2c47aa0905131337w4a338386t2407f7df7a398cf7@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: File system corruption 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: Wed, 13 May 2009 20:47:18 -0000 Pat Wendorf wrote: > I spoke too soon I guess: A buddy of mine at the hosting provider took down > the box and did a fsck -y on the var partition, this seems to have cleaned > it up. It looks like the regular fsck -p could not repair it. You may like to put fsck_y_enable="YES" in your /etc/rc.conf, though this does not affect the root volume.