On Thu, 4 Nov 2004, matt brennan wrote: > I created a new raid1 array on two 300GB disks but it came in > underweight in size... > > Filesystem 1M-blocks Used Available Use% Mounted on > /dev/md0 129013 27322 95137 23% /home Is the disk connected to an ATA-100 or 133 controller? IIRC, you will only see ~130MB unless it's a 133 controller... > I guess I stuffed up with the partitioning (from fdisk): > > > Disk /dev/hda: 255 heads, 63 sectors, 16709 cylinders > > Units = cylinders of 16065 * 512 bytes > > > > Device Boot Start End Blocks Id System > > /dev/hda1 1 16709 134215011 fd Linux raid autodetect > This was accepting fdisk's default max size. Check the cylinder/head/sector against the BIOS. If neccessary, you can use fdisk (or cfdisk) to force a change, but this will likely destroy any data on the disk. Also make sure both disks are partitioned identically - RAID1 will only be as big as the smallest of the partitions. It does look like fdisk has picked up the wrong CHS numbers - the disk only appears to be 127GB is size according to those. (255*63*16709*512)/(1024*1024*1024) = 127. Gordon - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
