Re: No syncing after crash. Is this a software raid bug?

[Kasper Dupont <48755289462761382922@expires.02.sep.2006.kasperd.net>]

> Why would you not be happy? resyncs in general are bad since they
> indicate your data is possibly out-of-sync and the resync itself
> consumes an enormous amount of resources

Of course reducing the amount of resources spend on syncing is
a good thing. But it shouldn't be done at the expense of less
reliability.

> This is a feature of new-ish md driver code that more aggressively marks
> the array as "clean" after writes

A bit too aggressive it seems. How can it end up being marked
clean when the two mirrors differ?

> The end result is that the array will most likely be "clean" in all
> circumstances even a crash, and you simply won't need to resync

Shouldn't it be unclean while an update is in progress? And if
it is how come I have been completely unable to trigger a resync
even when it was reset while disks were busy writing?

Here is the program I have used to verify if the two mirrors are
in sync: http://kasperd.net/~kasperd/raidtest.c
This program find that there is a difference between the two
mirrors.

-- 
Kasper Dupont -- Rigtige mænd skriver deres egne backupprogrammer
#define _(_)"d.%.4s%."_"2s" /* This is my new email address */
char*_="@2kaspner"_()"%03"_("4s%.")"t\n";printf(_+11,_+6,_,6,_+2,_+7,_+6);
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html