From owner-freebsd-current@FreeBSD.ORG Wed Nov 3 11:16:16 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 771C616A4CE for ; Wed, 3 Nov 2004 11:16:16 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 26B2443D45 for ; Wed, 3 Nov 2004 11:16:16 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iA3BFPIZ058767 for ; Wed, 3 Nov 2004 06:15:25 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iA3BFPfC058764 for ; Wed, 3 Nov 2004 06:15:25 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Wed, 3 Nov 2004 06:15:25 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: current@FreeBSD.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: recent spontaneous reboot on -current and 8 DUP I= in fsck. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Nov 2004 11:16:16 -0000 I had a spontaneous reboot a few days ago, with a -CURRENT from about a week ago. Cause unclear, and I was in X11, which doesn't simplify things. When it came back up, fsck was displeased with the state of the world: ** /dev/ad0s1e ** Last Mounted on /usr ** Phase 1 - Check Blocks and Sizes 8 DUP I=141 UNEXPECTED SOFT UPDATE INCONSISTENCY 5 DUP I=621 UNEXPECTED SOFT UPDATE INCONSISTENCY ... ** Phase 2 - Check Pathnames DUP/BAD I=621 OWNER=rwatson MODE=100644 SIZE=35491 MTIME=Jun 26 14:13 2003 FILE=/home/rwatson/freebsd/commit/RELENG_4/src/contrib/groff/man/groff_char.man UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? [yn] y ... ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts BAD/DUP FILE I=141 OWNER=rwatson MODE=100444 SIZE=1155 MTIME=Oct 24 19:34 2004 CLEAR? [yn] n ... What's odd here is that these files hadn't been touched in a week. I'm going to upgrade my notebook to a known source configuration (things a bit indeterminate here since I had a lot of local patches in odd places) and see about reproducing. Has anyone else seen this out of fsck? Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research