Fixes for RAID1 resync
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest5 patches 7 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | md/raid1: be more cautious where we read-balance during resync.drivers/ | +1 | 0 replies | |
| 2/5 | md/raid1: clean up request counts properly in close_sync()drivers/ | +5 | 0 replies | |
| 3/5 | md/raid1: make sure resync waits for conflicting writes to complete.drivers/ | +4 | 0 replies | |
| 4/5 | md/raid1: Don't use next_resync to determine how far resync has progresseddrivers/ | +5 | 0 replies | |
| 5/5 | md/raid1: update next_resync under resync_lock.drivers/ | +3 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/5] Fixes for RAID1 resync
This set of patches fixes all the issues that I could find with the new raid1 resync code.
I didn't find anything that would obviously fix the hang that Jon Brassow reported.
Jon: could you test with these patches on top of what you have just in case something happens to fix the problem without me realising it?
Eivind: if you could test too, I'd really appreciate it.
Thanks,
NeilBrown
---
NeilBrown (5):
md/raid1: be more cautious where we read-balance during resync. md/raid1: clean up request counts properly in close_sync() md/raid1: make sure resync waits for conflicting writes to complete. md/raid1: Don't use next_resync to determine how far resync has progressed md/raid1: update next_resync under resync_lock.
drivers/md/raid1.c | 33 +++++++++++++++++---------------- 1 file changed, 17 insertions(+), 16 deletions(-)
Signature · 1 line
Signature