/etc/mdtab looks like this:
# mdtab entry for /dev/md0
/dev/md0 raid0,8k,0,53200828 /dev/sde1 /dev/sdf1 /dev/sdg1
and mdadd/mdrun works fine:
#mdadd -a
REGISTER_DEV sde1 to md0 done
REGISTER_DEV sdf1 to md0 done
REGISTER_DEV sdg1 to md0 done
#mdrun -a
raid0 personality registered
raid0 : Allocating 8 bytes for hash.
but mke2fs fails miserably:
#mke2fs /dev/md0
....
Warning: could not write 8 blocks starting at 3948805 for inode table: No such file or directory
Warning: could not write 8 blocks starting at 3948813 for inode table: No such file or directory
Warning: could not write 8 blocks starting at 3948821 for inode table: No such file or directory
483/ 774Warning: could not write 8 blocks starting at 3956765 for inode table: No such file or directory
Warning: could not write 8 blocks starting at 3956773 for inode table: No such file or directory
Warning: could not write 8 blocks starting at 3956781 for inode table: No such file or directory
Warning: could not write 8 blocks starting at 3956789 for inode table: No such file or directory
Warning: could not write 8 blocks starting at 3956797 for inode table: No such file or directory
...screen after screen after screen of this...
changeing the md to use /dev/sde /dev/sdf /dev/sdg has no effect. using
the drives standalone works 100%
....any ideas?
clean 2.1.89, md 0.35
Drives are 3 of theese:
kernel: Vendor: QUANTUM Model: FIREBALL ST2.1S Rev: 0F0C
kernel: Type: Direct-Access ANSI SCSI revision: 02
kernel: Detected scsi disk sde at scsi0, channel 0, id 4, lun 0
Best regards, Tomas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu