From: Tycho Andersen <tycho@tycho.pizza>
To: Dave Chinner <david@fromorbit.com>
Cc: "Darrick J . Wong" <djwong@kernel.org>,
linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Tycho Andersen <tandersen@netflix.com>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH] xfs: don't do inodgc work if task is exiting
Date: Fri, 12 May 2023 09:16:36 -0600 [thread overview]
Message-ID: <ZF5YVNdeVNSoG08p@tycho.pizza> (raw)
In-Reply-To: <20230512014547.GA3223426@dread.disaster.area>
On Fri, May 12, 2023 at 11:45:47AM +1000, Dave Chinner wrote:
>
> Yeah, this is papering over the observed symptom, not addressing the
> root cause of the inodegc flush delay. What do you see when you run
> sysrq-w and sysrq-l? Are there inodegc worker threads blocked
> performing inodegc?
I will try this next time we encounter this.
> e.g. inodegc flushes could simply be delayed by an unlinked inode
> being processed that has millions of extents that need to be freed.
>
> In reality, inode reclaim can block for long periods of time
> on any filesystem, so the concept of "inode reclaim should
> not block when PF_EXITING" is not a behaviour that we guarantee
> anywhere or could guarantee across the board.
>
> Let's get to the bottom of why inodegc has apparently stalled before
> trying to work out how to fix it...
I'm happy to try, but I think it is also worth applying this patch.
Like I said in the other thread, having to evac a box to get rid of an
unkillable userspace process is annoying.
Thanks for the debugging tips.
Tycho
next prev parent reply other threads:[~2023-05-12 15:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 15:17 [PATCH] xfs: don't do inodgc work if task is exiting Tycho Andersen
2023-05-12 0:07 ` Darrick J. Wong
2023-05-12 15:15 ` Tycho Andersen
2023-05-12 22:54 ` Dave Chinner
2023-05-16 0:12 ` Dave Chinner
2023-05-16 14:00 ` Tycho Andersen
2023-05-12 1:45 ` Dave Chinner
2023-05-12 15:16 ` Tycho Andersen [this message]
2023-05-12 22:01 ` Dave Chinner
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=ZF5YVNdeVNSoG08p@tycho.pizza \
--to=tycho@tycho.pizza \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=tandersen@netflix.com \
/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