1. This tool totally ROCKS! On my "Hot Smokin' Weapon!" usefulness-O-meter, this pins the needle at "DUDE!!"
One of the things I really like about messing with Linux is that there are so many cool things you can do with it - because folks like you take the time to make it useful. Many thanks, moy Obligado, muchos Gracias, bolshoi Spasiba, merci beaucoup, etc. etc.
2. (the inevitable) Question: Assume I am creating a raid-5 array using a bunch of 1T drives as the array members. I fire off the mdadm command, it takes the parameters, chews for a millisecond or two, and then immediately returns with a success message indicating that the array is "running".
Normally, when a command like this returns (formatting a disk, for example), this means it's totally done, and the device is golden. However with mdadm, the command returns, but the array is still "building". Top shows "md0_raid5" and "md0_resync" in response to my create command using mdadm.
(a) Why does it do this?
(b) Besides looking at the drive lights (which can fool you) or leaving an instance of top running, how would I determine that the process has finished, and how do I know it finished correctly?
(c) If you gave an answer to the previous question about "partitions" in the mdadm context - could you re-post it? I'd sure like to know that as well.
Again thanks for everything!
Jim
