From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 6/8] gfs2: instrumentation wrt log_flush stuck
Date: Fri, 5 Jun 2020 12:14:57 -0400 (EDT) [thread overview]
Message-ID: <1003983013.31986358.1591373697538.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CAHc6FU6w_yu9VDC=ci2Yb6F3ngjF4DkT=SjB1ovkBTmd0O=76Q@mail.gmail.com>
----- Original Message -----
> On Fri, Jun 5, 2020 at 4:49 PM Bob Peterson <rpeterso@redhat.com> wrote:
> > Hi Andreas,
> >
> > ----- Original Message -----
> > (snip)
> > > > @@ -970,7 +969,16 @@ void gfs2_log_flush(struct gfs2_sbd *sdp, struct
> > > > gfs2_glock *gl, u32 flags)
> > > >
> > > > if (!(flags & GFS2_LOG_HEAD_FLUSH_NORMAL)) {
> > > > if (!sdp->sd_log_idle) {
> > > > + unsigned long start = jiffies;
> > > > +
> > > > for (;;) {
> > > > + if (time_after(jiffies, start + (HZ *
> > > > 600))) {
> > >
> > > This should probably have some rate limiting as well, for example:
> >
> > Seems unnecessary. If the log flush gets stuck, the message will be printed
> > once, and at most every 10 minutes.
>
> No, after ten minutes, the message will actually be printed for each
> iteration of the loop. That's exactly why I was suggesting the rate
> limiting.
No, after ten minutes it dumps the ail list so you can see the problem
and exits the loop with "break;".
The next time it enters the loop, it starts with a new value of start
which doesn't expire for another ten minutes.
Bob
next prev parent reply other threads:[~2020-06-05 16:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 13:05 [Cluster-devel] [PATCH 0/8] Misc Patch Collection Bob Peterson
2020-05-26 13:05 ` [Cluster-devel] [PATCH 1/8] gfs2: Don't ignore inode write errors during inode_go_sync Bob Peterson
2020-05-26 13:05 ` [Cluster-devel] [PATCH 2/8] gfs2: Allow lock_nolock mount to specify jid=X Bob Peterson
2020-05-26 13:05 ` [Cluster-devel] [PATCH 3/8] gfs2: add memory barriers to gfs2_glock_remove_revoke Bob Peterson
2020-05-26 13:05 ` [Cluster-devel] [PATCH 4/8] gfs2: Add new sysfs file for gfs2 status Bob Peterson
2020-05-26 13:05 ` [Cluster-devel] [PATCH 5/8] gfs2: print mapping->nrpages in glock dump for address space glocks Bob Peterson
2020-05-26 13:05 ` [Cluster-devel] [PATCH 6/8] gfs2: instrumentation wrt log_flush stuck Bob Peterson
2020-06-05 13:24 ` Andreas Gruenbacher
2020-06-05 14:48 ` Bob Peterson
2020-06-05 16:09 ` Andreas Gruenbacher
2020-06-05 16:14 ` Bob Peterson [this message]
2020-06-05 16:18 ` Andreas Gruenbacher
2020-05-26 13:05 ` [Cluster-devel] [PATCH 7/8] gfs2: Add new trace point for glock ail management Bob Peterson
2020-06-05 14:43 ` Andreas Gruenbacher
2020-05-26 13:05 ` [Cluster-devel] [PATCH 8/8] gfs2: introduce new gfs2_glock_assert_withdraw Bob Peterson
2020-06-05 14:38 ` [Cluster-devel] [PATCH 0/8] Misc Patch Collection Andreas Gruenbacher
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=1003983013.31986358.1591373697538.JavaMail.zimbra@redhat.com \
--to=rpeterso@redhat.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;
as well as URLs for NNTP newsgroup(s).