Allow event counters to be off by one
.. even without --force Signed-off-by: Neil Brown <neilb@suse.de>
This commit is contained in:
parent
773135f5bd
commit
ee04451c56
|
@ -369,7 +369,9 @@ int Assemble(struct supertype *st, char *mddev, int mdfd,
|
||||||
sparecnt=0;
|
sparecnt=0;
|
||||||
for (i=0; i< bestcnt ;i++) {
|
for (i=0; i< bestcnt ;i++) {
|
||||||
int j = best[i];
|
int j = best[i];
|
||||||
int event_margin = !force;
|
int event_margin = 1; /* always allow a difference of '1'
|
||||||
|
* like the kernel does
|
||||||
|
*/
|
||||||
if (j < 0) continue;
|
if (j < 0) continue;
|
||||||
/* note: we ignore error flags in multipath arrays
|
/* note: we ignore error flags in multipath arrays
|
||||||
* as they don't make sense
|
* as they don't make sense
|
||||||
|
|
|
@ -14,6 +14,10 @@ Changes Prior to this release
|
||||||
Thanks to Ross Vandegrift
|
Thanks to Ross Vandegrift
|
||||||
- --monitor now reports which device failed in a 'Fail' message
|
- --monitor now reports which device failed in a 'Fail' message
|
||||||
This broke with 2.6
|
This broke with 2.6
|
||||||
|
- Improve chance of array starting properly after a crash.
|
||||||
|
mdadm was insisting the event numbers were identical, but this
|
||||||
|
isn't needed, and is a problem if the crash was while the metadata
|
||||||
|
was being updated.
|
||||||
|
|
||||||
Changes Prior to 2.1 release
|
Changes Prior to 2.1 release
|
||||||
- Fix assembling of raid10 array when devices are missing.
|
- Fix assembling of raid10 array when devices are missing.
|
||||||
|
|
Loading…
Reference in New Issue