-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Umm you can't have different sized drives in the same raid 5 array.
Think about it, how would stripping and parity and everything work. My
guess is the 250GB id causing you problems, remove that drive from the
array and rebuild the array if needed, and all should be well. If you
really want to use the 250GB drive, make a 200GB partition on it, and
then add the 200GB partition to the array and you are free to use the
remaining 50GB for whatever, maybe LVM.

~J

Joseph Key wrote:
> I have a AMD system with 3 200G and 1 250G hard drive arranged in a 4 drive
> RAID 5 array. The 250G drive is connected to the /dev/hda, a DVD-RW on
> /dev/hdc, the other 200G drives in /dev/hde, /dev/hdg and /dev/hdi. Two of
> the controllers are ATA100/133 and the last is ATA66. /dev/hdi is connected
> to the ATA66 controller. I have reiserfs on /dev/md0 using the entire array.
> With this setup I have a read problem accessing files on the array. If I do
> an md5sum on a file less then 200M it is fine. If I md5sum on a file greater
> then 200M the results change every time I run it. Checking dmesg hda, hde
> and hdg are UDMA(100) and hdi is UDMA(66). /proc/mdstat shows the array as
> clean with all drives mounted. Any idea of what can be causing this problem?
> 
> Some history the array was built in degraded mode with hda, hde and hdg
> only. The data was copied over and a cmp was done on the original and copied
> data to insure it copied correctly. After the data move was verified. I took
> down the 2 disk lvm array and put one of the drives in the RAID 5 array as
> hdi. I then did a hot add of the new drive to complete the array. 
> 
> Joseph Key
> 
> 
> 
> _______________________________________________
> TCLUG Mailing List - Minneapolis/St. Paul, Minnesota
> tclug-list at mn-linux.org
> http://mailman.mn-linux.org/mailman/listinfo/tclug-list
> 

- --
Jonathan Kline <klinej at msoe.edu>
Milwaukee School of Engineering
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDHaRPQkF4UQaOvSoRAnKiAJ9K7/fWIQ0tTmFJHiF/Sd6klanpKgCg1aVH
eL6I1lQGDDpc80ej+Q5aDxA=
=FDR9
-----END PGP SIGNATURE-----