From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH] GFS2: Set log descriptor type for jdata blocks
Date: Tue, 28 May 2013 08:54:38 -0400 (EDT) [thread overview]
Message-ID: <1102208234.29508494.1369745678789.JavaMail.root@redhat.com> (raw)
In-Reply-To: <1369576275.2737.3.camel@menhir>
----- Original Message -----
| > This patch sets the log descriptor type according to whether the
| > journal commit is for (journaled) data or metadata. This was
| > recently broken when the functions to process data and metadata
| > log ops were combined.
| Thanks - looks good. If we can automatically detect the erroneous
| entries, could we also automatically deal with those too? That might be
| useful in case people already have such entries in their logs,
|
| Steve.
Hi,
Since the bad entries are data blocks, there's no good way to
distinguish them from other kinds of corrupt metadata. We could
make the code treat them as jdata rather than metadata instead of
throwing the error, but I question whether it's worth it, since the
problem will only present itself upon journal replay, and only on
recent upstream kernels. The problem doesn't exist in RHEL6 or below.
Removing our error checking in favor of treating the blocks as jdata
would make it less effective at finding real metadata block
corruption in the journals, and that seems like a check we should
keep. Still, it's simple enough to do. Opinions?
Regards,
Bob Peterson
Red Hat File Systems
next prev parent reply other threads:[~2013-05-28 12:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <450275516.28847125.1369421988473.JavaMail.root@redhat.com>
2013-05-24 19:02 ` [Cluster-devel] [GFS2 PATCH] GFS2: Set log descriptor type for jdata blocks Bob Peterson
2013-05-26 13:51 ` Steven Whitehouse
2013-05-28 12:54 ` Bob Peterson [this message]
2013-05-30 15:40 ` Bob Peterson
2013-05-30 15:40 ` Steven Whitehouse
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=1102208234.29508494.1369745678789.JavaMail.root@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).