From owner-freebsd-current Wed Nov 20 03:30:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA24490 for current-outgoing; Wed, 20 Nov 1996 03:30:12 -0800 (PST) Received: from veda.is (ubiq.veda.is [193.4.230.60]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA24472 for ; Wed, 20 Nov 1996 03:30:09 -0800 (PST) Received: (from adam@localhost) by veda.is (8.8.3/8.7.3) id LAA25850; Wed, 20 Nov 1996 11:32:27 GMT Date: Wed, 20 Nov 1996 11:32:27 GMT From: Adam David Message-Id: <199611201132.LAA25850@veda.is> To: taob@io.ORG (Brian Tao) Cc: freebsd-current@freebsd.org Subject: Re: "panic: nfs: sillyrename dir" References: X-Newsreader: NN version 6.5.0 #2 (NOV) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >/* > * Silly rename. To make the NFS filesystem that is stateless look a little > * more like the "ufs" a remove of an active vnode is translated to a rename > * to a funny looking filename that is removed by nfs_inactive on the > * nfsnode. There is the potential for another process on a different client > * to create the same funny name between the nfs_lookitup() fails and the > * nfs_rename() completes, but... > */ > But... what?!?! :) Was this double panic just a coincidence? Probably not relevant to the previous message... I am seeing .nfs* files left in the filesystem long after they are active, perhaps this simply results from rebooting the client machine? Other NFS oddities: I am also noticing 'make clean' sometimes needs to be repeated multiple times on an NFS mounted directory, because of an infamous "rm: directory not empty". 'make includes' with an NFS mounted /usr bails out sometimes complaining about nonexistent files which match a template of INS@* (from install). None of this is new. -- Adam David