storage: For task [manage the pools and volumes to match the specified state] We may need to wait the mdadm rsycn finished.

[FineFan]

Hi,

I think after we create the md ride , we need to wait for resync.
During the playbook running I was check the md status via "cat /proc/mdstat"
And I figure out that ,before the resync action finished ,we have done all of the steps and cleaned the test env.

I think we may need to wait the md ride finish its resync.
Wait the state become clean in "mdadm -D /dev/md127" before the next steps.

BR
Fine

[pcahyna]

Hello, how does the problem manifest itself? Is there any actual problem seen by the user?

[japokorn]

@FineFan You have mentioned test environment, so I guess you are worried that not waiting for RAID to resync could be an issue.

In storage role RAID resync is run by mdadm when RAID is created. Since mdadm man pages state that "The array can be used as soon as it has been created. There is no need to wait for the initial resync to finish.", I believe that there should be no issues involved.

Also RAID resync can take a very long time (~30 minutes for our tests, around three days for array of five 2TB disks) so
letting it finish is probably not something we would like to do.