From owner-freebsd-current  Wed Jul 26  6:36:27 2000
Delivered-To: freebsd-current@freebsd.org
Received: from mta5.snfc21.pbi.net (mta5.snfc21.pbi.net [206.13.28.241])
	by hub.freebsd.org (Postfix) with ESMTP id 9B34037BE98
	for <current@freebsd.org>; Wed, 26 Jul 2000 06:36:23 -0700 (PDT)
	(envelope-from gdinolt@pacbell.net)
Received: from pacbell.net ([63.199.30.114])
 by mta5.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9)
 with ESMTP id <0FYB00AYC4EOA1@mta5.snfc21.pbi.net> for current@freebsd.org;
 Wed, 26 Jul 2000 06:35:12 -0700 (PDT)
Date: Wed, 26 Jul 2000 06:35:57 -0700
From: "George W. Dinolt" <gdinolt@pacbell.net>
Subject: Re: Even with version 1.54 of mfs_vnops.c and a freshly built world
 and booted kernel (with ``options MFS''),
 I am still seeing these. What could I be missing?
To: mjacob@feral.com
Cc: current@freebsd.org, josb@corp.webtv.net
Message-id: <397EE93C.D81F08F2@pacbell.net>
MIME-version: 1.0
X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
X-Accept-Language: en
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Mahtew Jacob wrote:

>Hmm. They went away for me- I thought, but no, you're right. They're
still
>there. This is what I actually use to get rid of them:
>
>Index: mfs_vnops.c
>===================================================================
>RCS file: /home/ncvs/src/sys/ufs/mfs/mfs_vnops.c,v
>retrieving revision 1.53
>diff -u -r1.53 mfs_vnops.c
>--- mfs_vnops.c 2000/05/05 09:59:07     1.53
>+++ mfs_vnops.c 2000/07/25 21:47:09
>@@ -80,6 +80,7 @@
>        { &vop_reclaim_desc,            (vop_t *) mfs_reclaim },
>        { &vop_strategy_desc,           (vop_t *) mfs_strategy },
>        { &vop_unlock_desc,             (vop_t *) vop_defaultop },
>+       { &vop_getwritemount_desc,      (vop_t *) vop_stdgetwritemount
},
>        { NULL, NULL }
> };
> static struct vnodeopv_desc mfs_vnodeop_opv_desc =

I have applied the patch and rebuilt my kernel. This seems to have fixed
the problem for me. I will keep monitoring the situation. Maybe this can
get committed to -current?

Thanks,

George Dinolt




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