drive-mirror : wait that busy eq false before block-job-complete
When the drive-mirror is at 100%, and write occurs, the busy flag can change from false->true
- 100% no new writes
transferred:
1073741824 bytes remaining: 0 bytes total:
1073741824 bytes progression: 100.00 % busy: false
transferred:
1073741824 bytes remaining: 0 bytes total:
1073741824 bytes progression: 100.00 % busy: false
transferred:
1073741824 bytes remaining: 0 bytes total:
1073741824 bytes progression: 100.00 % busy: false
- 100% new writes
transferred:
1073741824 bytes remaining: 0 bytes total:
1073741824 bytes progression: 100.00 % busy: true
transferred:
1073741824 bytes remaining: 0 bytes total:
1073741824 bytes progression: 100.00 % busy: true
transferred:
1073741824 bytes remaining: 0 bytes total:
1073741824 bytes progression: 100.00 % busy: true
- 100% no new writes
transferred:
1073741824 bytes remaining: 0 bytes total:
1073741824 bytes progression: 100.00 % busy: false
transferred:
1073741824 bytes remaining: 0 bytes total:
1073741824 bytes progression: 100.00 % busy: false
transferred:
1073741824 bytes remaining: 0 bytes total:
1073741824 bytes progression: 100.00 % busy: false
So, we need to check that busy is false before doing the block-job-complete.
Also, we force the vm to pause, if it's busy for more than 120s when drive-mirror is at 100%
Signed-off-by: Alexandre Derumier <aderumier@odiso.com>