-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
storage: For task [manage the pools and volumes to match the specified state] We may need to wait the mdadm rsycn finished. #129
Comments
Hello, how does the problem manifest itself? Is there any actual problem seen by the user? |
@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 Also RAID resync can take a very long time (~30 minutes for our tests, around three days for array of five 2TB disks) so |
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
The text was updated successfully, but these errors were encountered: