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