From owner-freebsd-current@FreeBSD.ORG  Tue Jul 10 10:15:08 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: current@freebsd.org
Delivered-To: freebsd-current@FreeBSD.ORG
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 55DB416A400
	for <current@freebsd.org>; Tue, 10 Jul 2007 10:15:08 +0000 (UTC)
	(envelope-from vova@sw.ru)
Received: from vbook.fbsd.ru (swsoft-mipt-nat.sw.ru [195.214.233.10])
	by mx1.freebsd.org (Postfix) with ESMTP id 0887313C44C
	for <current@freebsd.org>; Tue, 10 Jul 2007 10:15:07 +0000 (UTC)
	(envelope-from vova@sw.ru)
Received: from vova by vbook.fbsd.ru with local (Exim 4.67 (FreeBSD))
	(envelope-from <vova@sw.ru>) id 1I8CkJ-0000pN-AF
	for current@freebsd.org; Tue, 10 Jul 2007 14:15:03 +0400
From: Vladimir Grebenschikov <vova@sw.ru>
To: current <current@freebsd.org>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Organization: SWsoft
Date: Tue, 10 Jul 2007 14:15:02 +0400
Message-Id: <1184062502.1478.14.camel@localhost>
Mime-Version: 1.0
X-Mailer: Evolution 2.10.2 FreeBSD GNOME Team Port 
Sender: Vladimir Grebenschikov <vova@swsoft.com>
Cc: 
Subject: Hard fsck failure on UFS2 after successefull background fsck
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2007 10:15:08 -0000

Hi

Following scenario give me re-predicable hard fsck failure (requires
manual intervention).

Filesystem:
/dev/ad0s2d on /usr (ufs, local, soft-updates)

1. System crash (nothing serious in disc write caches), idle or almost
idle before.

2. Boot, background fsck started and succeeded
Shutdown system gracefully.

3. Boot system, auto fsck failed:
Jul 10 00:43:51 vbook fsck: /dev/ad0s2d: INCORRECT BLOCK COUNT I=4103188 (4 should be 0) (CORRECTED)
Jul 10 00:43:51 vbook fsck: /dev/ad0s2d: INCORRECT BLOCK COUNT I=4103200 (4 should be 0) (CORRECTED)
Jul 10 00:43:51 vbook fsck: /dev/ad0s2d: INCORRECT BLOCK COUNT I=4145417 (4 should be 0) (CORRECTED)
Jul 10 00:43:51 vbook fsck: /dev/ad0s2d: INCORRECT BLOCK COUNT I=8902657 (24 should be 20) (CORRECTED)
Jul 10 00:43:51 vbook fsck: /dev/ad0s2d: INCORRECT BLOCK COUNT I=8903709 (12 should be 4) (CORRECTED)
Jul 10 00:43:51 vbook fsck: /dev/ad0s2d: INCORRECT BLOCK COUNT I=8903713 (12 should be 0) (CORRECTED)
Jul 10 00:43:51 vbook fsck: /dev/ad0s2d: INCORRECT BLOCK COUNT I=9091888 (4 should be 0) (CORRECTED)
Jul 10 00:43:51 vbook fsck: /dev/ad0s2d: INCORRECT BLOCK COUNT I=9092284 (324 should be 312) (CORRECTED)
Jul 10 00:43:51 vbook fsck: /dev/ad0s2d: MISSING '.'  I=7113130  OWNER=root MODE=40755
Jul 10 00:43:51 vbook fsck: /dev/ad0s2d: SIZE=512 MTIME=Jul  3 02:30 2007 
Jul 10 00:43:51 vbook fsck: /dev/ad0s2d: DIR=?
Jul 10 00:43:51 vbook fsck: 
Jul 10 00:43:51 vbook fsck: /dev/ad0s2d: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY.

Every time "MISSING '.'" error is reproduced.

I am only person expecting that problem ?

-- 
Vladimir B. Grebenschikov
SWsoft Inc. vova@swsoft.com