On Thu, 11 Jun 2009 00:23 +0200, "martin f krafft" <madd...@debian.org> wrote: > also sprach whollyg...@letterboxes.org <whollyg...@letterboxes.org> > [2009.06.10.2308 +0200]: > > So, if I understand correctly, in the Lenny version of mdadm > > (I never experienced this building arrays with mdadm on Etch) > > in order for the creation of an array to take place, one must > > run "mdadm -w <arrayx>" immediately after running "mdadm > > -C <arrayx> -n y -x z etcetc" otherwise the new array will just sit > > there not syncing the component devices until the first write? > > Yes, this is a safety measure, since -C only writes the superblocks > and then assembles the array as normal. This is postponed until > a write operation takes place in case in case the admin needs to > intervene.
I guess you need to be more of a power user than myself to imagine a scenario requiring intervention. But, I do understand what is happening on my machine, now. Thanks. will -- whollyg...@letterboxes.org -- http://www.fastmail.fm - Accessible with your email software or over the web -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
