From owner-freebsd-fs@FreeBSD.ORG Tue Sep 6 15:19:34 2005 Return-Path: X-Original-To: fs@freebsd.org Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C483D16A41F; Tue, 6 Sep 2005 15:19:34 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3BD2543D46; Tue, 6 Sep 2005 15:19:33 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id j86FJLAF033327; Tue, 6 Sep 2005 10:19:21 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <431DB382.7000904@centtech.com> Date: Tue, 06 Sep 2005 10:19:30 -0500 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.11) Gecko/20050904 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robert Watson References: <200509051953.22337@aldan> <20050906114055.R51625@fledge.watson.org> <200509060931.33977@aldan> <20050906144512.T75104@fledge.watson.org> In-Reply-To: <20050906144512.T75104@fledge.watson.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/1066/Tue Sep 6 06:42:41 2005 on mh1.centtech.com X-Virus-Status: Clean Cc: questions@freebsd.org, fs@freebsd.org, Mikhail Teterin Subject: Re: Strange case of filesystem corruption? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Sep 2005 15:19:34 -0000 Robert Watson wrote: > On Tue, 6 Sep 2005, Mikhail Teterin wrote: > >> On Tuesday 06 September 2005 06:51 am, Robert Watson wrote: >> = Have you recently experienced a system crash or hard reboot without >> proper >> = shutdown? >> >> According to dmesg.boot, this filesystem was flagged as "not properly >> dismounted" back then. The machine's uptime is currently 47 days and >> no background fskcs are running, of course. >> >> Yours analysis is, likely, correct then... I guess, the fix should be >> MFCed. (What about 6.0-release?) Thanks! > > > The change was made in HEAD before the 6.x branch, so it's currently in > RELENG_6. I fired off an e-mail to Kirk to ask about MFC'ing it to > RELENG_5, and will do so once I hear back, assuming he thinks there is > no reason not to. > > Do you have back logs to when bgfsck was running, btw? Normally it > should correct this sort of thing, suggestion that bgfsck exited without > correcting them, which is a little worrying. You may want to boot to > single user and fsck manually... I thought that having background_fsck="NO" in your rc.conf would make the partition get mounted even though it is unclean, and no fsck's would happen (I use this 'feature' right now, since doing bgfsck on a 2TB partition takes about 2 hours just to make the snapshot, which means filesystem activity is suspended for that time). If it was set to "YES", and bgfsck exited abnormally, I don't think it will get mounted automatically, so he would have had to manually mount it, correct? Mikhail, do any of those scenario's sound like a match? Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------