From owner-freebsd-current Mon Feb 15 10:55:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13802 for freebsd-current-outgoing; Mon, 15 Feb 1999 10:55:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA13781; Mon, 15 Feb 1999 10:55:54 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA18501; Mon, 15 Feb 1999 10:54:24 -0800 (PST) (envelope-from dillon) Date: Mon, 15 Feb 1999 10:54:24 -0800 (PST) From: Matthew Dillon Message-Id: <199902151854.KAA18501@apollo.backplane.com> To: "Jose M. Alcaide" Cc: freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: easily reproducible NFS-related panic References: <36C8526D.9987934@we.lc.ehu.es> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Sorry for the cross-posting, but I am running -STABLE and I would :like to hear from -CURRENT users about this problem. : :The panic is easily reproducible: simply, try to hard-link a file :from a local filesystem to a NFS-mounted one (yes, I _know_ that :this is non-sense): :.. : : mount remotesys:/exportedfs /mnt : cd /mnt : ln /bin/ls . --> this complaints about cross-device link, OK : ln /bin/ls . --> (yes, again) : panic: vrele: negative ref cnt --> CRASH!!! : :I have confirmed this with recent 3.0-STABLE and 3.1-BETA clients :and servers, and also with a Solaris 2.5.1 NFS server. However, :it does not happen on a 2.2.8-RELEASE client. : :Some feedback from the NFS gurus ;-) would be very useful. : :-- JMA :----------------------------------------------------------------------- :José Mª Alcaide | mailto:jose@we.lc.ehu.es :Universidad del País Vasco | mailto:jmas@es.FreeBSD.ORG This was fixed yesterday. Get the latest -stable and see if it still occurs. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message