On Thursday July 7, [EMAIL PROTECTED] wrote: > Hi Neil! > Thanks much for your help, array creation using devel-2 just works, > however, the array can't be assembled again after it's stopped:(
Hmm, yeh, nor it can :-( I'm not sure when I'll have time to look at this (I'm on leave at the moment with family visiting and such) but I'll definitely get back to you by Thursday if not before. Thanks, NeilBrown > > # mdadm --zero-superblock -e 1 /dev/sdb > # mdadm --zero-superblock -e 1 /dev/sdc > # /bin/rm -rf /bitmap > # mdadm -C /dev/md0 -e 1 --bitmap /bitmap -l 1 -n 2 /dev/sdb /dev/sdc > mdadm: array /dev/md0 started. > # more /proc/mdstat > Personalities : [raid1] > md0 : active raid1 sdc[1] sdb[0] > 33554424 blocks [2/2] [UU] > [>....................] resync = 0.6% (206400/33554424) > finish=16.1min s > peed=34400K/sec > bitmap: 4096/4096 pages [16384KB], 4KB chunk, file: /bitmap > > unused devices: <none> > # mdadm -S /dev/md0 > # more /proc/mdstat > Personalities : [raid1] > unused devices: <none> > # mdadm -A /dev/md0 -e 1 --bitmap /bitmap /dev/sdb /dev/sdc > mdadm: device 1 in /dev/md0 has wrong state in superblock, but /dev/sdc seems > ok > mdadm: failed to add /dev/sdc to /dev/md0: Invalid argument > mdadm: failed to add /dev/sdb to /dev/md0: Invalid argument > mdadm: /dev/md0 assembled from 0 drives - not enough to start the array. > (even if you stop the array after resync completes, it doesn't matter > as expected). - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
