From owner-freebsd-bugs  Tue Mar  7 23: 1:28 2000
Delivered-To: freebsd-bugs@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id C5F8C37B56F; Tue,  7 Mar 2000 23:01:26 -0800 (PST)
	(envelope-from bde@FreeBSD.org)
Received: (from bde@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id XAA32946;
	Tue, 7 Mar 2000 23:01:26 -0800 (PST)
	(envelope-from bde@FreeBSD.org)
Date: Tue, 7 Mar 2000 23:01:26 -0800 (PST)
From: <bde@FreeBSD.org>
Message-Id: <200003080701.XAA32946@freefall.freebsd.org>
To: leon@obsidian.co.za, bde@FreeBSD.org, freebsd-bugs@FreeBSD.org
Subject: Re: kern/16490: Attempted listing of just-mounted ext2fs causes kernel panic
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Synopsis: Attempted listing of just-mounted ext2fs causes kernel panic

State-Changed-From-To: open->feedback
State-Changed-By: bde
State-Changed-When: Tue Mar 7 22:47:17 PST 2000
State-Changed-Why: 
This is probably caused by the filesystem being mke2fs'd with the "filetype"
feature.  This feature was unsupported, and unsupported features used to
cause panics.  This feature is now supported in both -stable and -current,
and unsupported features now cause mount failures.

Do you still have the problem?  Current versions of dumpe2fs show the
feature list.  The default features are "filetype" and "sparse".  The
latter is unsupported so it will now cause a mount failure.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message