Re: MFS complains that no vop_getwritemount operation(?)

2000-07-17 Thread Makoto MATSUSHITA


sheldonh> Have you sent your patch to Kirk McKusick <[EMAIL PROTECTED]>?

No, not yet. It seems that this change is incoroprated with FFS
snapshots feature, but I cannot decide it's true or not; other
filesystem are modified also (see commitlogs), but mfs is not changed...

Anyway, I'll try to email later.

-- -
Makoto `MAR' MATSUSHITA


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: MFS complains that no vop_getwritemount operation(?)

2000-07-17 Thread Sheldon Hearn



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 <[EMAIL PROTECTED]>?

> 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 [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



MFS complains that no vop_getwritemount operation(?)

2000-07-15 Thread Makoto MATSUSHITA


Preamble: 5-current CVSuped Jun/15/2000 04:00 JST from cvsup.jp.FreeBSD.org

Rebuild my kernel and reboot, then I've got following message:

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).

--- src/sys/ufs/mfs/mfs_vnops.c.distSat May  6 03:30:59 2000
+++ src/sys/ufs/mfs/mfs_vnops.c Sun Jul 16 00:52:43 2000
@@ -76,6 +76,7 @@
{ &vop_islocked_desc,   (vop_t *) vop_defaultop },
{ &vop_lock_desc,   (vop_t *) vop_defaultop },
{ &vop_open_desc,   (vop_t *) mfs_open },
+   { &vop_getwritemount_desc,  (vop_t *) vop_stdgetwritemount },
{ &vop_print_desc,  (vop_t *) mfs_print },
{ &vop_reclaim_desc,(vop_t *) mfs_reclaim },
{ &vop_strategy_desc,   (vop_t *) mfs_strategy },

Does anyone can reproduce mfs_badop[vop_getwritemount] warnings ?

-- -
Makoto `MAR' MATSUSHITA


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message