From owner-freebsd-current Mon Jul 17 7:19:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.2.163]) by hub.freebsd.org (Postfix) with ESMTP id 3E4EC37B798 for ; Mon, 17 Jul 2000 07:19:31 -0700 (PDT) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.15 #1) id 13EBjY-0005l2-00; Mon, 17 Jul 2000 16:19:00 +0200 From: Sheldon Hearn To: Makoto MATSUSHITA Cc: current@FreeBSD.ORG Subject: Re: MFS complains that no vop_getwritemount operation(?) In-reply-to: Your message of "Sun, 16 Jul 2000 01:11:16 +0900." <20000716011116B.matusita@jp.FreeBSD.org> Date: Mon, 17 Jul 2000 16:19:00 +0200 Message-ID: <22135.963843540@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 16 Jul 2000 01:11:16 +0900, Makoto MATSUSHITA wrote: > Jul 16 00:48:32 martini /kernel: mfs_badop[vop_getwritemount] > Jul 16 00:48:32 martini /kernel: mfs_badop[vop_getwritemount] = 45 > > I'm using MFS as /tmp filesystem, and this message shows up if I > access to /tmp directory such as create a file/directory. > > Following patch seems to shut up my kernel, but I dunno it is the > right fix for this problem (I've got a hint from ../ufs/ufs_vnops.c). Have you sent your patch to Kirk McKusick ? > Does anyone can reproduce mfs_badop[vop_getwritemount] warnings ? Yes, I got them until I switched to a malloc(9)-backed md(4) device. They seemed harmless. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message