Date: Thu, 08 Jun 1995 12:37:56 +0900 From: ohki@gssm.otsuka.tsukuba.ac.jp To: davidg@Root.COM Cc: freebsd-bugs@FreeBSD.org, ohki@gssm.otsuka.tsukuba.ac.jp Subject: Re: 2.0.5-ALPHA crashes with 'panic: vm_object_deallocate: ...' Message-ID: <199506080337.MAA00509@smri01.gssm.otsuka.tsukuba.ac.jp> In-Reply-To: Your message of "Wed, 07 Jun 1995 20:13:17 MST" References: <199506080313.UAA00470@corbin.Root.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
David Greenman writes: > 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 reporte > d > on the server? Is the filesystem mounted 'soft'? > > -DG Every time a user invokes /usr/ucb/mail command on NFS client machine, the message is logged on that client machine. But, other kinds of messages are never logged, except 'file lock is not supported'. clinet machine mount the filesystem 'softly', via auto mounter. I re-read a man page of mount_nfs of solaris, and found that soft mount may cause unexpected I/O error. I'm afraid my situation might be this case ( though the message appears very predictable way).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199506080337.MAA00509>