looks like you ran mke2fs on your partitions, then you did mkraid on them.
guess what? raid code puts a little chunk of info about each disk and the raid
array it is part of onto the end of the partition, and then reports the size
of the device as being a little smaller than the number of blocks on the disk.
raid is a block device, e2fs is a file system. you have to make the raid
first, then the fs on top of that.
so, you need to run mke2fs on /dev/md0, rather than the individual partitions,
then you should be fine.
allan
Jason Lin <[EMAIL PROTECTED]> said:
> I am trying to setup RAID 1 on RedHat6.1.
>
> "fsck /dev/md0" gives the following:
>
> Parallelizing fsck version 1.15 (18-Jul-1999)
> e2fsck 1.15, 18-Jul-1999 for EXT2 FS 0.5b, 95/08/09
> The filesystem size (according to the superblock) is
> 757055 blocks
> The physical size of the device is 757024 blocks
> Either the superblock or the partition table is likely
> to be corrupt!
> Abort<y>?
> -------------------------------------
> But the constituent disks have 757055 blocks each.
> Should I do "mkraid --really-force /dev/md0" ?
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Talk to your friends online with Yahoo! Messenger.
> http://im.yahoo.com
>
