[Top] [All Lists]

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

To: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Subject: Re: [PATCH] xfs: don't trigger fsync log force based on inode pin count
From: Brian Foster <bfoster@xxxxxxxxxx>
Date: Wed, 22 Apr 2015 13:13:23 -0400
Cc: xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <20150422161509.GA27237@xxxxxxxxxxxxx>
References: <1429713466-22137-1-git-send-email-bfoster@xxxxxxxxxx> <20150422161509.GA27237@xxxxxxxxxxxxx>
User-agent: Mutt/1.5.23 (2014-03-12)
On Wed, Apr 22, 2015 at 09:15:09AM -0700, Christoph Hellwig wrote:
> 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.

Yeah, that's a good point. I noticed that in xfs_trans_log_inode() when
debugging but didn't think much about it since I reproduced on v4. I can
get performance back with the aforementioned cil push fix, but if the
path forward is behavior where the inode is going to be logged anyways,
that is decent reason to emulate such behavior in the pre-v5 case.

Note that we have the following in xfs_bmapi_write():

        if (bma.logflags)
                xfs_trans_log_inode(tp, ip, bma.logflags);

... and some other places. I don't reproduce this particular problem on
v5, so something else might be logging the inode here. That strikes me
as not what we want with regard to the change count, however..


> _______________________________________________
> xfs mailing list
> xfs@xxxxxxxxxxx
> http://oss.sgi.com/mailman/listinfo/xfs

<Prev in Thread] Current Thread [Next in Thread>