This is the the same as "ignore recovery_offset if bitmap exists", describing
how I hit the problem (before attempting to put a patch together to fix it).
Nate
On 10/30/2015 11:58 AM, Jes Sorensen wrote:
Nate Dailey <nate.dailey@xxxxxxxxxxx> writes:
I've found that if I interrupt a recovery by removing the target
device, do IO before the recovery checkpoint, then re-add the device
and let the recovery complete, the mismatch_cnt is non-zero after
doing a check.
Neil,
While I am on the nagging path, here is another one.
Jes
Here's exactly what I'm doing:
- create a 5 GB raid1 with internal bitmap
- do a check, verify zero mismatch_cnt
- remove one member device
- dd 256MB with 2GB seek
- lower sync_speed_min/max to 500
- re-add removed device
- wait 15 sec
- remove the same member device again
- dd 1MB with 1 GB seek
- restore sync_speed_min/max to system defaults
- re-add removed device
- when recovery competes, do another check
At this point the mismatch_cnt is non-zero.
I originally hit this on RHEL 7.1, but tested 4.1.1 from kernel.org
and it happens there too.
I'm out of my league in terms of trying to fix this, but would be
happy to test a fix. I wonder if it's really necessary to resume a
bitmap recovery from the checkpoint? Wouldn't the bitmap always
reflect what needs to be copied?
Nate
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
