From: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
To: Eyal Lebedinsky <eyal@eyal.emu.id.au>
Cc: linux-raid@vger.kernel.org
Subject: Re: Reliability of bitmapped resync
Date: Mon, 23 Feb 2009 22:36:46 +0100 [thread overview]
Message-ID: <20090223213646.GA18555@lazy.lzy> (raw)
In-Reply-To: <49A3128F.9020708@eyal.emu.id.au>
Hi,
> Did you mean
> echo repair > /sys/block/md0/md/sync_action
>
> I run 'check' regularly and I am rather sure that it reports but does not fix the mismatches.
the sequence is as follow:
1) disk removed.
2) disk re-added
3) _automatic_ resync
4) manual check (after the resync finished)
The last check returns mismatches.
bye,
--
piergiorgio
prev parent reply other threads:[~2009-02-23 21:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 19:40 Reliability of bitmapped resync Piergiorgio Sartor
2009-02-23 19:59 ` NeilBrown
2009-02-23 20:19 ` Piergiorgio Sartor
2009-02-23 21:31 ` NeilBrown
2009-02-23 21:40 ` Piergiorgio Sartor
2009-02-23 21:49 ` NeilBrown
2009-02-24 19:39 ` Piergiorgio Sartor
2009-02-25 2:39 ` Neil Brown
2009-02-25 18:51 ` Piergiorgio Sartor
2009-03-13 17:19 ` Bill Davidsen
2009-02-23 21:18 ` Eyal Lebedinsky
2009-02-23 21:36 ` Piergiorgio Sartor [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=20090223213646.GA18555@lazy.lzy \
--to=piergiorgio.sartor@nexgo.de \
--cc=eyal@eyal.emu.id.au \
--cc=linux-raid@vger.kernel.org \
/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).