Date: Wed, 20 Nov 1996 11:32:27 GMT From: Adam David <adam@veda.is> To: taob@io.ORG (Brian Tao) Cc: freebsd-current@freebsd.org Subject: Re: "panic: nfs: sillyrename dir" Message-ID: <199611201132.LAA25850@veda.is> References: <Pine.BSF.3.95.961115181627.16615A-100000@cabal.io.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>/* > * 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 <adam@veda.is>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611201132.LAA25850>