NetBSD Problem Report #28722

From www@netbsd.org  Mon Dec 20 15:14:39 2004
Return-Path: <www@netbsd.org>
Received: by narn.netbsd.org (Postfix, from userid 31301)
	id 7F30E63B843; Mon, 20 Dec 2004 15:14:39 +0000 (UTC)
Message-Id: <20041220151439.7F30E63B843@narn.netbsd.org>
Date: Mon, 20 Dec 2004 15:14:39 +0000 (UTC)
From: joff@embeddedARM.com
Reply-To: joff@embeddedARM.com
To: gnats-bugs@netbsd.org
Subject: fsck_ext2fs dies with "bad inode number 0 to ginode"
X-Send-Pr-Version: www-1.0

>Number:         28722
>Category:       bin
>Synopsis:       fsck_ext2fs dies with "bad inode number 0 to ginode"
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Dec 20 15:15:00 +0000 2004
>Originator:     Jesse Off
>Release:        2.99.11
>Organization:
>Environment:
>Description:
Filled up my ext2fs filesystem and kernel panic'ed.  Upon restart fsck_ext2fs does the following and dies (without fixing the filesystem):

# fsck_ext2fs -y /dev/wd0e
** /dev/rwd0e
** Last Mounted on
** Root file system
** Phase 1 - Check Blocks and Sizes
182967 DUP I=44680
** Phase 1b - Rescan For More DUPS
182967 DUP I=14889
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
UNREF DIR  I=83845  OWNER=root MODE=40755
SIZE=4096 MTIME=Dec 17 03:19 2004
RECONNECT? yes

NO lost+found DIRECTORY
CREATE? yes

bad inode number 0 to ginode

>How-To-Repeat:

>Fix:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD: gnats_config.sh,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.