From owner-freebsd-bugs Wed Jun 7 20:13:32 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA29032 for bugs-outgoing; Wed, 7 Jun 1995 20:13:32 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id UAA29023 for ; Wed, 7 Jun 1995 20:13:28 -0700 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id UAA05564; Wed, 7 Jun 1995 20:16:48 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id UAA00470; Wed, 7 Jun 1995 20:13:41 -0700 Message-Id: <199506080313.UAA00470@corbin.Root.COM> To: ohki@gssm.otsuka.tsukuba.ac.jp cc: freebsd-bugs@FreeBSD.org Subject: Re: 2.0.5-ALPHA crashes with 'panic: vm_object_deallocate: ...' In-reply-to: Your message of "Thu, 08 Jun 95 11:50:44 +0900." <199506080250.LAA00405@smri01.gssm.otsuka.tsukuba.ac.jp> From: David Greenman Reply-To: davidg@Root.COM Date: Wed, 07 Jun 1995 20:13:17 -0700 Sender: bugs-owner@FreeBSD.org Precedence: bulk > I replaced nfs_serv.c (Id: nfs_serv.c,v 1.14.2.1 1995/06/07 07:25:09 davigd), > and then, NFS server machine (named utogw) does not crash anymore. > But NFS client machine (named smb, running solaris 2.3) complains > with the message > >Jun 8 11:22:09 smb unix: NFS write error on host utogw: I/O error. >Jun 8 11:22:09 smb unix: (file handle: >Jun 8 11:22:09 smb unix: 5040000 >Jun 8 11:22:09 smb unix: 1000000 >Jun 8 11:22:09 smb unix: c000000 >Jun 8 11:22:09 smb unix: 48150000 >Jun 8 11:22:09 smb unix: 7047d52f >Jun 8 11:22:09 smb unix: 0 >Jun 8 11:22:09 smb last message repeated 2 times >Jun 8 11:22:09 smb unix: ) > > Do you have any idea? Does it happen often or is it a transient error? The only thing I know of off hand that might cause this (other than faulty hardware) is an attempt to write to a directory file, but this is unlikely. Are there any errors reported on the server? Is the filesystem mounted 'soft'? -DG