From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [gfs2-utils PATCH 00/11] Misc patches regarding corrupt rindex handling
Date: Thu, 25 Feb 2016 12:04:27 -0500 [thread overview]
Message-ID: <cover.1456419237.git.rpeterso@redhat.com> (raw)
Hi,
These patches are probably best handled as separate items, rather than as
a set, but I didn't want to send out 11 separate emails.
This is a collection of patches I developed while debugging some rather
complex problems involving the rebuilding of corrupt or missing rindex
system files by fsck.gfs2. It also fixes some problems whereby gfs2_edit
or other utils crash and burn due to corrupt rindex files.
Regards,
Bob Peterson
Red Hat File Systems
Signed-off-by: Bob Peterson <rpeterso@redhat.com>
---
Bob Peterson (11):
libgfs2: Backport rbtree fixes from upstream
libgfs2: Check for obvious corruption reading rindex
libgfs2: Change rgrp counts to be uint64_t
gfs2_edit: Don't reference an empty rgrp tree
fsck.gfs2: Read jindex before making rindex repairs
fsck.gfs2: better reporting of false positive rgrp identification
fsck.gfs2: Minor reformatting
fsck.gfs2: Ditch variable rgcount_from_index
fsck.gfs2: Add ability to fix rindex file size
fsck.gfs2: Do not try to overrun the max rgrps that fit inside rindex
fsck.gfs2: Detect multiple rgrp grow segments
gfs2/edit/hexedit.c | 9 +-
gfs2/fsck/fs_recovery.c | 138 +++++++++++++++++++
gfs2/fsck/fs_recovery.h | 1 +
gfs2/fsck/initialize.c | 142 +-------------------
gfs2/fsck/rgrepair.c | 349 ++++++++++++++++++++++++++++++++++--------------
gfs2/include/osi_tree.h | 51 ++++---
gfs2/libgfs2/gfs2l.c | 2 +-
gfs2/libgfs2/libgfs2.h | 3 +-
gfs2/libgfs2/rgrp.c | 30 +++--
gfs2/libgfs2/super.c | 8 +-
10 files changed, 457 insertions(+), 276 deletions(-)
--
2.5.0
next reply other threads:[~2016-02-25 17:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 17:04 Bob Peterson [this message]
2016-02-25 17:04 ` [Cluster-devel] [gfs2-utils PATCH 01/11] libgfs2: Backport rbtree fixes from upstream Bob Peterson
2016-02-25 17:04 ` [Cluster-devel] [gfs2-utils PATCH 02/11] libgfs2: Check for obvious corruption reading rindex Bob Peterson
2016-02-25 17:04 ` [Cluster-devel] [gfs2-utils PATCH 03/11] libgfs2: Change rgrp counts to be uint64_t Bob Peterson
2016-02-25 17:04 ` [Cluster-devel] [gfs2-utils PATCH 04/11] gfs2_edit: Don't reference an empty rgrp tree Bob Peterson
2016-02-25 17:04 ` [Cluster-devel] [gfs2-utils PATCH 05/11] fsck.gfs2: Read jindex before making rindex repairs Bob Peterson
2016-02-25 17:04 ` [Cluster-devel] [gfs2-utils PATCH 06/11] fsck.gfs2: better reporting of false positive rgrp identification Bob Peterson
2016-02-25 17:04 ` [Cluster-devel] [gfs2-utils PATCH 07/11] fsck.gfs2: Minor reformatting Bob Peterson
2016-02-25 17:04 ` [Cluster-devel] [gfs2-utils PATCH 08/11] fsck.gfs2: Ditch variable rgcount_from_index Bob Peterson
2016-02-25 17:04 ` [Cluster-devel] [gfs2-utils PATCH 09/11] fsck.gfs2: Add ability to fix rindex file size Bob Peterson
2016-02-25 17:04 ` [Cluster-devel] [gfs2-utils PATCH 10/11] fsck.gfs2: Do not try to overrun the max rgrps that fit inside rindex Bob Peterson
2016-02-25 17:04 ` [Cluster-devel] [gfs2-utils PATCH 11/11] fsck.gfs2: Detect multiple rgrp grow segments Bob Peterson
2016-03-15 17:47 ` [Cluster-devel] [gfs2-utils PATCH 00/11] Misc patches regarding corrupt rindex handling Andrew Price
2016-03-21 14:53 ` Bob Peterson
2016-03-21 16:44 ` Andrew Price
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=cover.1456419237.git.rpeterso@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.