cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [gfs2-utils PATCH 0/7] fsck.gfs2: cannot fix directory with same leaf at multiple different offsets in hash table
Date: Tue, 16 Jul 2013 07:56:07 -0500	[thread overview]
Message-ID: <1373979374-20650-1-git-send-email-rpeterso@redhat.com> (raw)

Hi,

Here is a set of 7 patches that address some recently discovered problems
in fsck.gfs2. Most of these problems had to do with directory metadata in
which the same leaf block appeared multiple times within the same hash
table (I've only seen one instance):

[gfs2-utils PATCH 1/7] fsck.gfs2: Fix reference to uninitialized
[gfs2-utils PATCH 2/7] fsck.gfs2: fix some log messages
[gfs2-utils PATCH 3/7] fsck.gfs2: Fix directory link on relocated
[gfs2-utils PATCH 4/7] fsck.gfs2: Fix infinite loop in pass1b caused
[gfs2-utils PATCH 5/7] fsck.gfs2: don't check newly created
[gfs2-utils PATCH 6/7] fsck.gfs2: avoid negative number in leaf depth
[gfs2-utils PATCH 7/7] fsck.gfs2: Detect and fix duplicate references

Regards,

Bob Peterson
Red Hat File Systems



                 reply	other threads:[~2013-07-16 12:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1373979374-20650-1-git-send-email-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 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).