From: Carlos Maiolino <cmaiolino@redhat.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: linux-xfs@vger.kernel.org, david@fromorbit.com, bfoster@redhat.com
Subject: Re: [PATCH 2/3] xfs: drop IDONTCACHE on inodes when we mark them sick
Date: Wed, 9 Jun 2021 10:55:05 +0200 [thread overview]
Message-ID: <20210609085505.j2isfiydym7aabqz@omega.lan> (raw)
In-Reply-To: <20210608152146.GR2945738@locust>
On Tue, Jun 08, 2021 at 08:21:46AM -0700, Darrick J. Wong wrote:
> On Tue, Jun 08, 2021 at 04:59:48PM +0200, Carlos Maiolino wrote:
> > Hi,
> >
> > On Sun, Jun 06, 2021 at 10:54:17AM -0700, Darrick J. Wong wrote:
> > > From: Darrick J. Wong <djwong@kernel.org>
> > >
> > > When we decide to mark an inode sick, clear the DONTCACHE flag so that
> > > the incore inode will be kept around until memory pressure forces it out
> > > of memory. This increases the chances that the sick status will be
> > > caught by someone compiling a health report later on.
> > >
> > > Signed-off-by: Darrick J. Wong <djwong@kernel.org>
> >
> > The patch looks ok, so you can add:
> >
> > Reviewed-by: Carlos Maiolino <cmaiolino@redhat.com>
> >
> >
> > Now, I have a probably dumb question about this.
> >
> > by removing the I_DONTCACHE flag, as you said, we are increasing the chances
> > that the sick status will be caught, so, in either case, it seems not reliable.
> > So, my dumb question is, is there reason having these inodes around will benefit
> > us somehow? I haven't read the whole code, but I assume, it can be used as a
> > fast path while scrubbing the FS?
>
> Two answers to your question: In the short term, preserving the incore
> inode means that a subsequent reporting run (xfs_spaceman -c 'health')
> is more likely to pick up the sickness report.
>
> In the longer term, I intend to re-enable reclamation of sick inodes
> by aggregating the per-inode sick bit in the per-AG health status so
> that reporting won't be interrupted by memory demand:
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git/log/?h=indirect-health-reporting
>
> (I haven't rebased that part in quite a while though.)
Thanks!
>
> --D
>
> >
> > Cheers.
> >
> > > ---
> > > fs/xfs/xfs_health.c | 9 +++++++++
> > > 1 file changed, 9 insertions(+)
> > >
> > >
> > > diff --git a/fs/xfs/xfs_health.c b/fs/xfs/xfs_health.c
> > > index 8e0cb05a7142..806be8a93ea3 100644
> > > --- a/fs/xfs/xfs_health.c
> > > +++ b/fs/xfs/xfs_health.c
> > > @@ -231,6 +231,15 @@ xfs_inode_mark_sick(
> > > ip->i_sick |= mask;
> > > ip->i_checked |= mask;
> > > spin_unlock(&ip->i_flags_lock);
> > > +
> > > + /*
> > > + * Keep this inode around so we don't lose the sickness report. Scrub
> > > + * grabs inodes with DONTCACHE assuming that most inode are ok, which
> > > + * is not the case here.
> > > + */
> > > + spin_lock(&VFS_I(ip)->i_lock);
> > > + VFS_I(ip)->i_state &= ~I_DONTCACHE;
> > > + spin_unlock(&VFS_I(ip)->i_lock);
> > > }
> > >
> > > /* Mark parts of an inode healed. */
> > >
> >
> > --
> > Carlos
> >
>
--
Carlos
next prev parent reply other threads:[~2021-06-09 8:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-06 17:54 [PATCHSET v3 0/3] xfs: preserve inode health reports for longer Darrick J. Wong
2021-06-06 17:54 ` [PATCH 1/3] xfs: only reset incore inode health state flags when reclaiming an inode Darrick J. Wong
2021-06-08 14:55 ` Carlos Maiolino
2021-06-06 17:54 ` [PATCH 2/3] xfs: drop IDONTCACHE on inodes when we mark them sick Darrick J. Wong
2021-06-07 1:40 ` Dave Chinner
2021-06-08 14:59 ` Carlos Maiolino
2021-06-08 15:21 ` Darrick J. Wong
2021-06-09 8:55 ` Carlos Maiolino [this message]
2021-06-06 17:54 ` [PATCH 3/3] xfs: selectively keep sick inodes in memory Darrick J. Wong
2021-06-07 1:43 ` Dave Chinner
2021-06-08 15:02 ` Carlos Maiolino
-- strict thread matches above, loose matches on Subject: below --
2021-06-03 3:12 [PATCHSET v2 0/3] xfs: preserve inode health reports for longer Darrick J. Wong
2021-06-03 3:12 ` [PATCH 2/3] xfs: drop IDONTCACHE on inodes when we mark them sick Darrick J. Wong
2021-06-03 4:34 ` Dave Chinner
2021-06-03 20:49 ` Darrick J. Wong
2021-06-03 12:23 ` Brian Foster
2021-06-03 20:48 ` Darrick J. Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210609085505.j2isfiydym7aabqz@omega.lan \
--to=cmaiolino@redhat.com \
--cc=bfoster@redhat.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).