Date: Tue, 24 Sep 1996 15:15:49 -0700 (PDT) From: nsayer@quack.kfu.com To: FreeBSD-gnats-submit@freebsd.org Subject: kern/1676: NFS V3 client causes panic Message-ID: <199609242215.PAA04244@morpheus.kfu.com> Resent-Message-ID: <199609242220.PAA21282@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 1676 >Category: kern >Synopsis: NFS V3 client causes panic >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Sep 24 15:20:04 PDT 1996 >Last-Modified: >Originator: Nick Sayer >Organization: just me >Release: FreeBSD 2.2-960801-SNAP i386 >Environment: NFS server is stock 2.2-960801-SNAP P-Pro 200 w/ AHA-2940 & 3G partition Client is Solaris 2.5.1 on SS10 >Description: Solaris defaults to using NFS V3. Aparently, so does this snapshot, since I did nothing I know of in the kernel config to ask for it (options NFS, FAILSAFE among others, but nothing about V3) >How-To-Repeat: solaris# mount -o rw,soft,bg,intr freebsd:/foo /mnt solaris# cd /mnt solaris# ls At this point the FreeBSD machine panics with ufs_ihashget: recursive lock not expected -- pid %d Adding vers=2 to the -o list in the mount prevents this. >Fix: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609242215.PAA04244>