Re: ffs_newvnode: inode has non zero blocks

[coypu%SDF.ORG@localhost]

On Wed, Nov 02, 2016 at 10:50:51PM +0200, Andreas Gustafsson wrote:
> coypu%SDF.ORG@localhost wrote:
> > There was recently an issue with resize_ffs mishandling a non zero
> > filled expansion of FFSv2 (PR 51116). I wonder if this is similar.
> > 
> > i.e., does zeroing out the disk help?
> 
> If I read the code of the test case correctly, it involves growing a
> file system image stored in a file, causing the file to grow
> correspondingly.  Since the expansion does not even exist in the image
> file prior before resize_ffs is run, there is no way for it to have
> non-zero content.
> -- 
> Andreas Gustafsson, gson%gson.org@localhost

The lengthy problem description is not very important as it was fixed
I am just wondering about the setup of the tests, if there's a
possibility of bad data being left over (reuse of image, etc.)