Date: Wed, 07 Jun 1995 20:13:17 -0700 From: David Greenman <davidg@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: ...' Message-ID: <199506080313.UAA00470@corbin.Root.COM> In-Reply-To: Your message of "Thu, 08 Jun 95 11:50:44 %2B0900." <199506080250.LAA00405@smri01.gssm.otsuka.tsukuba.ac.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199506080313.UAA00470>