From owner-freebsd-stable@FreeBSD.ORG Thu May 14 13:02:55 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 D2B2A1065670 for ; Thu, 14 May 2009 13:02:55 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 1F7A08FC18 for ; Thu, 14 May 2009 13:02:54 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id QAA13251; Thu, 14 May 2009 16:02:46 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4A0C1675.4090609@icyb.net.ua> Date: Thu, 14 May 2009 16:02:45 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.21 (X11/20090406) MIME-Version: 1.0 To: Andrew Snow References: <2c2c47aa0905121110i6355930bwce3a9c6afb117d4d@mail.gmail.com> <200905131124.16897.milu@dat.pl> <2c2c47aa0905131337w4a338386t2407f7df7a398cf7@mail.gmail.com> <4A0B31A2.9030805@modulus.org> In-Reply-To: <4A0B31A2.9030805@modulus.org> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 7bit Cc: Pat Wendorf , 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: Thu, 14 May 2009 13:02:56 -0000 on 13/05/2009 23:46 Andrew Snow said the following: > 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. This would make fsck -y run on all filesystems (clean, just checked, always ro, etc) iff fsck -p fails. This can be dangerous too if filesystem state is such that fsck gets confused. -- Andriy Gapon