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

Christoph Hellwig hch at infradead.org
Wed Apr 22 11:15:09 CDT 2015


On Wed, Apr 22, 2015 at 10:37:46AM -0400, Brian Foster wrote:
> There are probably a couple different ways to handle this. We could log
> the inode in the bmap cases in order to preserve the pincount check.

I'd favor that.  For one performance should be better, second we really
need to dirty the inode anyway for v5 file systems as that's the
mechanism used to increment di_changecount.



More information about the xfs mailing list