All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/2] repair: fixes for 3.2.0-rc2
Date: Fri,  9 May 2014 11:17:00 +1000	[thread overview]
Message-ID: <1399598222-4349-1-git-send-email-david@fromorbit.com> (raw)

Hi folks,

A couple of fixes identified for xfs_repair follow. The first is a
regression introduced by the discontiguous buffer support in the
prefetch code, which Eric Sandeen found. I've written a slightly
different fix for it than Eric did, but the concept for the fix is
all Eric's work.

The second patch is not actually a regression, but the filesystem
that triggered the above regression can't actually be repaired in a
sane amount of time because of an array insertion algorithm with
exponential cost. It's trivial to fix, and it means xfs_repair can
actually run to completion quickly rather than burn CPU for hours
getting nothing done.

These fixes mean I'll probably release a 3.2.0-rc3 once they've been
reviewed and go into the tree....

Cheers,

Dave.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2014-05-09  1:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-09  1:17 Dave Chinner [this message]
2014-05-09  1:17 ` [PATCH 1/2] repair: don't unlock prefetch tree to read discontig buffers Dave Chinner
2014-05-09  2:14   ` Eric Sandeen
2014-05-09  3:53     ` Dave Chinner
2014-05-09  1:17 ` [PATCH 2/2] repair: don't grind CPUs with large extent lists Dave Chinner
2014-05-09  3:01   ` Eric Sandeen
2014-05-09  3:56     ` Dave Chinner
2014-05-09  4:18       ` Eric Sandeen

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=1399598222-4349-1-git-send-email-david@fromorbit.com \
    --to=david@fromorbit.com \
    --cc=xfs@oss.sgi.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.