NetBSD Problem Report #8785

Received: (qmail 11596 invoked from network); 12 Nov 1999 20:40:09 -0000
Message-Id: <199911122038.WAA01392@kolster.fi>
Date: Fri, 12 Nov 1999 22:38:55 +0200 (EET)
From: Antti Kantee <pooka@iki.fi>
Reply-To: pooka@iki.fi
To: gnats-bugs@gnats.netbsd.org
Subject: ext2fs revision 1 not supported
X-Send-Pr-Version: 3.95

>Number:         8785
>Category:       kern
>Synopsis:       ext2fs revision 1 not supported
>Confidential:   no
>Severity:       non-critical
>Priority:       high
>Responsible:    bouyer
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Nov 12 12:42:00 +0000 1999
>Closed-Date:    Wed Feb 09 16:33:44 +0000 2000
>Last-Modified:  Wed Feb 09 16:34:10 +0000 2000
>Originator:     Antti Kantee
>Release:        -current ~Nov 9th
>Organization:
>Environment:
System: NetBSD/i386 1.4M


>Description:

	mount -t ext2fs /dev/wd2e /mnt
	Nov 12 21:13:24 babylon5 /netbsd: Ext2 fs: unsupported revision number: 1 (expected 0)

>How-To-Repeat:

	see above
>Fix:

	love to
>Release-Note:
>Audit-Trail:

From: Antti Kantee <pooka@iki.fi>
To: gnats-bugs@netbsd.org
Cc: Manuel Bouyer <bouyer@antioche.lip6.fr>
Subject: kern/8785
Date: Sat, 20 Nov 1999 00:41:23 +0200

 Actually I'm not absolutely sure that this is problem between ext2fs
 revisions. Today I did mke2fs -r 0 (which explicitly tells it to
 construct a rev 0 filesystem) and I happily mounted it on my
 NetBSD-current. wow! panic. Here's the trace:

 (gdb) where
 #0  0xf024f9b0 in db_last_command ()
 #1  0x3150000 in ?? ()
 #2  0xf01dc87b in cpu_reboot (howto=256, bootstr=0x0)
     at ../../../../arch/i386/i386/machdep.c:1215
 #3  0xf010ff4f in db_sync_cmd () at ../../../../ddb/db_command.c:593
 #4  0xf010fc70 in db_command (last_cmdp=0xf024f9b0,
 cmd_table=0xf024f7f0)
     at ../../../../ddb/db_command.c:295
 #5  0xf010fdca in db_command_loop () at ../../../../ddb/db_command.c:486
 #6  0xf0112782 in db_trap (type=1, code=0) at
 ../../../../ddb/db_trap.c:78
 #7  0xf01da788 in kdb_trap (type=1, code=0, regs=0xf8effc04)
     at ../../../../arch/i386/i386/db_interface.c:120
 #8  0xf01e2648 in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -266154776, 
       tf_esi = 256, tf_ebp = -118490052, tf_ebx = -118490020, tf_edx = 15360, 
       tf_ecx = 3840, tf_eax = 0, tf_trapno = 1, tf_err = 0, 
       tf_eip = -266491836, tf_cs = 8, tf_eflags = 514, tf_esp = -118490032, 
       tf_ss = -267165423, tf_vm86_es = -263471104, tf_vm86_ds = 0, 
       tf_vm86_fs = -126267392, tf_vm86_gs = -118489976})
     at ../../../../arch/i386/i386/trap.c:298
 #9  0xf0100d05 in calltrap ()
 #10 0xf0136111 in panic (fmt=0xf022cce8 "ext2fs_dirbadentry")
     at ../../../../kern/subr_prf.c:215
 #11 0xf01b0f47 in ext2fs_dirbadentry (dp=0xf8fe4e00, de=0xf8795000, 
     entryoffsetinblock=0) at ../../../../ufs/ext2fs/ext2fs_lookup.c:736
 #12 0xf01b07e3 in ext2fs_lookup (v=0xf8effd74)
     at ../../../../ufs/ext2fs/ext2fs_lookup.c:396
 #13 0xf014cec7 in lookup (ndp=0xf8effedc) at
 ../../../../sys/vnode_if.h:71
 #14 0xf014cbbb in namei (ndp=0xf8effedc) at
 ../../../../kern/vfs_lookup.c:153
 #15 0xf01542a8 in vn_open (ndp=0xf8effedc, fmode=5, cmode=2240)
     at ../../../../kern/vfs_vnops.c:127
 #16 0xf01507c0 in sys_open (p=0xf8eef3c0, v=0xf8efff88, retval=0xf8efff80)
     at ../../../../kern/vfs_syscalls.c:963
 #17 0xf01e2cfa in syscall (frame={tf_es = 31, tf_ds = 31, tf_edi = -272654124, 
       tf_esi = -272654124, tf_ebp = -272656416, tf_ebx = 1209059536, 
       tf_edx = -272654124, tf_ecx = 134734368, tf_eax = 5, tf_trapno = 3, 
       tf_err = 2, tf_eip = 1208977599, tf_cs = 23, tf_eflags = 530, 
       tf_esp = -272656844, tf_ss = 31, tf_vm86_es = 0, tf_vm86_ds = 0, 
       tf_vm86_fs = 0, tf_vm86_gs = 0}) at
 ../../../../arch/i386/i386/trap.c:760
 #18 0xf0100dbd in syscall1 ()

 If I get real bored tomorrow I'll try running a kernel without
 DIAGNOSTIC and see where I can get with that.

   -Antti

From: Antti Kantee <pooka@iki.fi>
To: gnats-bugs@netbsd.org, Manuel Bouyer <bouyer@antioche.lip6.fr>
Cc:  Subject: kern/8785
Date: Sat, 20 Nov 1999 18:34:39 +0200

 Just for the record, I tried mounting the filesystem described earlier
 on a 2.0.30 linux and succeeded. ls, however, failed with almost the
 exact same message as on NetBSD:

 EXT2-fs error (device 16:01): ext2_find_entry: bad entry in directory #2: rec_len is too small for name_len - offset=0, inode=2, rec_len=12, name_len=513
 /bin/ls: .: No such file or directory

 I put up diffs between linux 2.0.30 (on which I couldn't get anything
 out of the filesystem) and 2.2.13 (on which the filesystem worked)
 ext2fs at http://www.iki.fi/pooka/NetBSD/ext2fsdiffs.gz just in case
 someone wants to look at them.

   -Antti
Responsible-Changed-From-To: kern-bug-people->bouyer 
Responsible-Changed-By: bouyer 
Responsible-Changed-When: Tue Jan 25 06:33:39 PST 2000 
Responsible-Changed-Why:  
I'm working on this 
State-Changed-From-To: open->feedback 
State-Changed-By: bouyer 
State-Changed-When: Fri Jan 28 09:46:57 PST 2000 
State-Changed-Why:  
Just added support to -current. Please test ! 
State-Changed-From-To: feedback->closed 
State-Changed-By: bouyer 
State-Changed-When: Wed Feb 9 08:33:44 PST 2000 
State-Changed-Why:  
Solved. 
>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.