On Wed, Dec 3, 2008 at 4:57 AM, Frank Batschulat (Home) <Frank.Batschulat at sun.com> wrote: > On Tue, 02 Dec 2008 23:04:39 +0100, Mike Gerdts <mgerdts at gmail.com> wrote: > >> Unless there is some long-latent bug in CVS, this looks to be a >> regression in the NFSv3 client. > > quite possibly: > > nfs3_inactive can leave .nfsXXX files behind > http://bugs.opensolaris.org/view_bug.do?bug_id=5029852
Ahh... search term should have been .nfsXXX rather than .nfs. :) The bug says that the problem exists in 5.10 as well but I have been unable to reproduce on S10u4 (different network topology) or S10u6 (same network topology) against the same NFS file system. Is there something that changed in Nevada that would cause this condition to be triggered more frequently? Thank you for tracking this down for me. -- Mike Gerdts http://mgerdts.blogspot.com/
