Commit "db91ff55bdf06736b" using curr_resync_completed instead of curr_resync when interrupted the resync operation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Neil,
>commit db91ff55bdf06736b849afc1b1fce5763bbb8d5d
>    1/ If a resync is aborted we should record how far we got
>     (recovery_cp) the last request that we know has completed
>     (->curr_resync_completed) rather than the last request that was
>     submitted (->curr_resync).
If resync operation interrupted,it will call:
>	wait_event(mddev->recovery_wait, !atomic_read(&mddev->recovery_active));
So the curr_resync must be complete. Using curr_resync is safe.
--------------
majianpeng?韬{.n?????%??檩??w?{.n???{炳盯w???塄}?财??j:+v??????2??璀??摺?囤??z夸z罐?+?????w棹f



[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux