Re: [PATCH] xfs: don't trigger fsync log force based on inode pin count

Brian Foster
2015-04-22T22:11:16Z

On Wed, Apr 22, 2015 at 03:06:11PM -0700, Christoph Hellwig wrote:
> On Wed, Apr 22, 2015 at 06:02:44PM -0400, Brian Foster wrote:
> > That was what I thought at first but I bumped the extent count a couple
> > times and still couldn't reproduce. I was curious enough to track it
> > down and it is actually the time update again. For whatever reason, I
> > think the crc mechanism is throwing the timing off and just hiding the
> > problem again. E.g., no-op xfs_vn_time_update() and the problem
> > reproduces on v5 as well.
>
> Actually, its the changecount again. If MS_I_VERSION is set
> the VFS will always call into ->xfs_vn_time_update.

Ah, I see. Yeah, that explains the time update then...