From owner-freebsd-fs@FreeBSD.ORG  Tue Sep  6 13:46:34 2005
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 B927E16A420;
	Tue,  6 Sep 2005 13:46:34 +0000 (GMT)
	(envelope-from rwatson@FreeBSD.org)
Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53])
	by mx1.FreeBSD.org (Postfix) with ESMTP id F279A43D6A;
	Tue,  6 Sep 2005 13:46:30 +0000 (GMT)
	(envelope-from rwatson@FreeBSD.org)
Received: from fledge.watson.org (fledge.watson.org [204.156.12.50])
	by cyrus.watson.org (Postfix) with ESMTP id 5734546B92;
	Tue,  6 Sep 2005 09:46:30 -0400 (EDT)
Date: Tue, 6 Sep 2005 14:46:30 +0100 (BST)
From: Robert Watson <rwatson@FreeBSD.org>
X-X-Sender: robert@fledge.watson.org
To: Mikhail Teterin <mi+kde@aldan.algebra.com>
In-Reply-To: <200509060931.33977@aldan>
Message-ID: <20050906144512.T75104@fledge.watson.org>
References: <200509051953.22337@aldan>
	<20050906114055.R51625@fledge.watson.org>
	<200509060931.33977@aldan>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: questions@freebsd.org, fs@freebsd.org
Subject: Re: Strange case of filesystem corruption?
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Sep 2005 13:46:34 -0000

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...

Robert N M Watson