From owner-freebsd-current Sun Jul 26 17:13:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01815 for freebsd-current-outgoing; Sun, 26 Jul 1998 17:13:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hoser (root@in221.inetnebr.com [199.184.119.221]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA01796 for ; Sun, 26 Jul 1998 17:13:01 -0700 (PDT) (envelope-from cradek@in221.inetnebr.com) Message-Id: X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Cc: fluffy@int.tele.dk Subject: Re: ext2fs and sync panic, still In-reply-to: Your message of "Sun, 26 Jul 1998 16:06:26 CDT." Date: Sun, 26 Jul 1998 19:12:31 -0500 From: Chris Radek Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 26 Jul 1998 16:06:26 CDT, Chris Radek writes: > I have run into the problem where mounting an ext2fs r/w panics as > soon as sync is called. r/o has no problems. This is from current > as of a couple days ago. Is it sane to reply to yourself? I hope so. The problem is that ext2_sync is trying to sync vnodes of type VNON (which have no associated inode and hence NULL v_data). The following patch fixes the panic: % diff -u ext2_vfsops.c.orig ext2_vfsops.c --- ext2_vfsops.c.orig Sun Jul 26 19:48:29 1998 +++ ext2_vfsops.c Sun Jul 26 20:14:15 1998 @@ -854,6 +854,8 @@ goto loop; if (VOP_ISLOCKED(vp)) continue; + if (vp->v_type == VNON) + continue; ip = VTOI(vp); if ((ip->i_flag & (IN_ACCESS | IN_CHANGE | IN_MODIFIED | IN_UPDATE)) == 0 && To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message