From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Assertion failure: sdp->sd_log_blks_free <= sdp->sd_jdesc->jd_blocks
Date: Wed, 27 Mar 2019 13:04:29 -0400 (EDT) [thread overview]
Message-ID: <605688868.15773477.1553706269793.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <529b370d-bf7b-64eb-dd84-acc567299070@citrix.com>
Hi Ross,
----- Original Message -----
> > I think the problem may actually be a regression with patch 588bff95c94ef.
>
> I still hit the assertion with this patch. gfs2_log_write_header() is
> unconditionally called and it calls gfs2_log_bmap() which changes
> sd_log_flush_head in the success path.
Hi Ross,
Okay, it looks like I really screwed up patch 588bff95c94ef. The patch
I posted yesterday is grossly inadequate and that code path needs some major
fixing. I'm in the process of getting it fixed properly. Sorry I didn't
cc you on that last patch. I'll cc you on the new one when it's ready, but
it may take a couple hours to get it ready.
Regards,
Bob Peterson
Red Hat File Systems
prev parent reply other threads:[~2019-03-27 17:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 18:17 [Cluster-devel] Assertion failure: sdp->sd_log_blks_free <= sdp->sd_jdesc->jd_blocks Ross Lagerwall
2019-03-19 18:48 ` Bob Peterson
2019-03-22 18:15 ` Ross Lagerwall
2019-03-25 15:29 ` Bob Peterson
2019-03-27 14:40 ` Ross Lagerwall
2019-03-27 17:04 ` Bob Peterson [this message]
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=605688868.15773477.1553706269793.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).