All of lore.kernel.org
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Robert Buchholz <robert.buchholz@goodpoint.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH RESEND] Fix and extend raid6check repair
Date: Mon, 10 Sep 2012 17:39:25 +1000	[thread overview]
Message-ID: <20120910173925.3e995909@notabene.brown> (raw)
In-Reply-To: <2586585.1GSuNNC3Ge@peanut>

[-- Attachment #1: Type: text/plain, Size: 1474 bytes --]

On Wed, 15 Aug 2012 14:55:43 +0200 Robert Buchholz
<robert.buchholz@goodpoint.de> wrote:

> Hello,
> 
> this is a resend of my patches dated Jul 20th in the "Find mismatch in 
> data blocks during raid6 repair" thread.
> 
> Currently, the raid6check tool does not compile (due to the xmalloc 
> changes) and my initial set of repair patches are faulty.  Please merge 
> and see my original emails for extended comments
> http://thread.gmane.org/gmane.linux.raid/38922/focus=39454
> http://thread.gmane.org/gmane.linux.raid/38922/focus=39460
> 
> 
> 
> Cheers
> 
> Robert

Hi,
 sorry for the long delay in getting to these.
They mostly look OK.  However:

1/ They way you added 'autorepair' as a new, final positional parameter is
not good.  I understand why you did it (it was easy) but I think we really
need to bite the bullet and introduce proper "getopt" parameter parsing.

2/ your new test scripts (thanks for including them!!) call 
   blockdev --flushbufs $md0
  after
    mdadm -S $md0
  This is pointless. Once $md0 is stopped, there can be no bufs to flush.
  I don't think there is any point in the 'udevadm settle' 'flushbufs' and
  'drop_caches' at the end.

I've applied your patches but if you could send updates to address those
issues, I'd appreciate it.

Also: please send one patch per email, preferably in-line (not an
attachment).  It makes it easier to reply to and also easier to apply.

Thanks,
NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

      reply	other threads:[~2012-09-10  7:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-15 12:55 [PATCH RESEND] Fix and extend raid6check repair Robert Buchholz
2012-09-10  7:39 ` NeilBrown [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=20120910173925.3e995909@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=robert.buchholz@goodpoint.de \
    /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.