Re: kern/51447: nullfs seems to not delete files properly

[David Holland <dholland-bugs%netbsd.org@localhost>]

The following reply was made to PR kern/51447; it has been noted by GNATS.

From: David Holland <dholland-bugs%netbsd.org@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: kern/51447: nullfs seems to not delete files properly
Date: Mon, 5 Sep 2016 18:22:39 +0000

 On Sat, Aug 27, 2016 at 01:05:01PM +0000, Joerg Sonnenberger wrote:
  >  On Sat, Aug 27, 2016 at 11:30:02AM +0000, coypu%sdf.org@localhost wrote:
  >  > >Synopsis:       nullfs seems to not delete files properly
  >  
  >  I think this description is a bit misleading. I'm seeing similar issues,
  >  where references remain to removed files. David suggested that some of
  >  the nullfs nodes might remain in cached. That would be useful to verify
  >  if you can reproduce this problem. E.g. the current explination is that
  >  the vnode on the real filesystem is referenced by the nullfs vnode and
  >  the nullfs vnode is only left alive by some cache.
 
 Right, that's expected behavior (though not desirable) -- the ffs
 vnode won't be reclaimed until the nullfs vnode "using" it goes away.
 However, this shouldn't result in ENOENT from a subsequent mkdir...
 
 Also, for directories, nullfs could (and I guess doesn't) flush its
 own vnodes after rmdir and unlink.
 
 -- 
 David A. Holland
 dholland%netbsd.org@localhost