Date: Mon, 17 Mar 1997 12:23:51 +0100 (CET) From: mickey@deadline.snafu.de To: FreeBSD-gnats-submit@freebsd.org Subject: kern/3010: NFS crashes client machine without trace Message-ID: <m0w6aW7-000400C@deadline.snafu.de> Resent-Message-ID: <199703171130.DAA05832@freefall.freebsd.org>
index | next in thread | raw e-mail
>Number: 3010
>Category: kern
>Synopsis: 3.0-current NFS client machine crashes without any trace.
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Mon Mar 17 03:30:01 PST 1997
>Last-Modified:
>Originator: Andreas S. Wetzel
>Organization:
Private system
>Release: FreeBSD 3.0-CURRENT i386
>Environment:
Client machine is a 3.0-current as of 03/16/97 with an NFS mounted
/usr/ports filesystem which comes from a FreeBSD 3.0 machine which
runs a -current that is 2-3 months older.
>Description:
Doing a ''make clean'' in /usr/ports/x11/xview-config on the NFS
client machine, after it has previously been extracted and built,
causes the NFS client machine to crash without any trace. I suppose
this happens due to heavy I/O especially when using this port, since
the original archive is somewhat huge. Doing the ''make clean''
on the NFS server machine did not show any unexpected behaviour.
>How-To-Repeat:
Take an older 3.0-current equipped NFS server machine and mount
/usr/ports from that server onto a fresh -current machine as a client.
Then cd /usr/ports/x11/xview-config and try to ''make extract configure''
and afterwards ''make clean''.
This crashed both of my NFS client machines which both mount /usr/ports
from a somewhat older 3.0-current NFS server.
One machine is a 486 DX2/66 the other is a 586/133 machine. Both
machines rebooted without warning message or else.
>Fix:
No idea about that.
>Audit-Trail:
>Unformatted:
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m0w6aW7-000400C>