From owner-freebsd-current Sun Jun 28 11:57:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25286 for freebsd-current-outgoing; Sun, 28 Jun 1998 11:57:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from coredump.int.tele.dk (fw1.inet.tele.dk [193.163.158.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25241 for ; Sun, 28 Jun 1998 11:57:07 -0700 (PDT) (envelope-from fluffy@int.tele.dk) Received: from localhost (fluffy@localhost) by coredump.int.tele.dk (8.8.8/8.8.8) with SMTP id UAA00380 for ; Sun, 28 Jun 1998 20:57:05 +0200 (CEST) (envelope-from fluffy@int.tele.dk) X-Authentication-Warning: coredump.int.tele.dk: fluffy owned process doing -bs Date: Sun, 28 Jun 1998 20:57:04 +0200 (CEST) From: Charlie Fluffy Reply-To: Barry Bouwsma To: freebsd-current@FreeBSD.ORG Subject: ext2fs and sync Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just built me 3.0-980627-SNAP, with support enabled for the Linux ext2fs filesystem. Mounting an ext2fs filesystem read-only seems to work fine, however monting the same filesystem rw results in a panic soon after. The problem appears to be easy to bring about with the `sync' command, and I see reference to ext2_sync+0xa6 Does anyone else see this, or do I need to dig around some more for the message about bad magic I think I saw once? Thanks, Barry Bouwsma, Tele Danmark Internet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message