Comment 1 for bug 491377
Revision history for this message
| Aryeh Gregor (simetrical+launchpad) wrote Re: mdadm uses one more spare that specified while creating a RAID5 array | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
From the man page:
When creating a RAID5 array, mdadm will automatically create a degraded array with an extra spare drive. This is because building the spare into a degraded array is in general faster than resyncing the parity on a non-degraded, but not clean, array. This feature can be overridden with the --force option.
I admit that I don't understand this at all (spotted this bug while looking for something else), but thought it might be helpful.