> > >> Hi all, >> >> Today I installed 16 fresh Western Digital WD5000BEVT (2,5") drives in >> one >> of our test servers. >> >> I created a software raid5 with a hotspare on these 16 disks. >> >> I noticed that the detection of the disks during boottime was very very >> slow. >> Creating the md superblocks went very very slow. >> >> After that all seemed fine (speed of the raid5 init was normal). >> >> I noticed many of these messages in the syslog (also attached): >> >> Mar 31 14:34:17 test ata_id[3752]: main: HDIO_GET_IDENTITY failed for >> '/dev/.tmp-8-112' >> Mar 31 14:34:17 test ata_id[3765]: main: HDIO_GET_IDENTITY failed for >> '/dev/.tmp-8-128' >> >> This seems to correspond to the slow detection of the disks. >> >> Is this an ATA problem, or a problem in the mvsas driver? >> >> I use the mvsas driver from 2.6.32 with the latest patch from Srinivas. >> >> Kind regards, >> Caspar Smit >> >> >> [Jack] It's normal behavior of SATA disk, SATA disk need more time than >> SAS >> disk to spin up to response command. > > I use loads of other SATA disks which don't have this behavior. > > Caspar > > > [Jack] In my test, some big SATA disks(ie 500G above)have this issues. > Best Regards There is definatly something wrong because an: mkfs -t xfs -f /dev/md0 takes around 15! minutes to complete. Normally this would take 15 seconds or so. Caspar Smit > > ************************************************************************ > Jack Wang > > -- > To unsubscribe from this list: send the line "unsubscribe linux-scsi" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
