From owner-freebsd-current Mon Jun 29 02:51:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA12550 for freebsd-current-outgoing; Mon, 29 Jun 1998 02:51:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA12535 for ; Mon, 29 Jun 1998 02:51:12 -0700 (PDT) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id JAA01257; Mon, 29 Jun 1998 09:49:58 GMT Date: Mon, 29 Jun 1998 18:49:58 +0900 (JST) From: Michael Hancock To: Barry Bouwsma cc: freebsd-current@FreeBSD.ORG Subject: Re: ext2fs and sync In-Reply-To: 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 Ext2fs has gotten stale it really hasn't been brought fully up to date since the lite2 changes, softupdates, maybe some vm changes, etc. We could use a ext2fs volunteer. Regards, Mike Hancock On Sun, 28 Jun 1998, Charlie Fluffy wrote: > 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