On Wed, 03 Dec 2008 12:53:34 +0100, Mike Gerdts <mgerdts at gmail.com> wrote:
> 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 interesting indeed. > something that changed in Nevada that would cause this condition to be > triggered more frequently? nothing I'm aware of yet as far as V3 is concerned, though that does not mean there's nothing new in a different path ;-) what we do have already, but for V4 is: NFSv4 clients leave too many .nfsXXX files around http://bugs.opensolaris.org/view_bug.do?bug_id=6636160 though it specifically claims using V3 cures the problem... so this must be something rather new or yet unknown, would it be possible to reproduce this somehow ? --- frankB
