Hi Caspar, I will check it once and let you know. But it will take some time to analyze this. --Srini. -----Original Message----- From: Caspar Smit [mailto:c.smit@xxxxxxxxxx] Sent: Friday, April 09, 2010 9:22 PM To: Srinivas Naga Venkatasatya Pasagadugula - ERS, HCL Tech Cc: linux-scsi@xxxxxxxxxxxxxxx Subject: Still havind major MVSAS issues. Hi Srinivas (and others), I'm still having troubles with SATA disks using the mvsas driver. Maybe you read my previous posts about the WD disks. The problem is easyly recreated: 1) Create a software raidset (i used a 5 disk raid6 as a test) 2) Create an XFS filesystem on it. (mkfs.xfs -f /dev/md0) I used the 2.6.32 kernel source using your patch. I get these messages: [ 5855.816019] drivers/scsi/mvsas/mv_sas.c 1631:mvs_query_task:rc= 5 [ 5857.820002] mvsas 0000:04:00.0: Phy7 : No sig fis [ 5858.024006] drivers/scsi/mvsas/mv_sas.c 1585:mvs_I_T_nexus_reset for device[4]:rc= 0 [ 5858.024014] ata12: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00 [ 5858.028001] ata12.00: device reported invalid CHS sector 0 [ 5858.028001] ata12: status=0x01 { Error } [ 5858.028001] ata12: error=0x04 { DriveStatusError } [ 7201.988017] ata18: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00 [ 7201.988114] ata18: status=0x01 { Error } [ 7201.988276] ata18: error=0x04 { DriveStatusError } Especially the latest 3 messages I got loads more of those on another set of disks. The creation of an XFS filesystem can take up to 15 minutes in stead of the normal 15 seconds! When I use the stock 2.6.32 kernel driver without your patch i get these errors: [ 6384.816015] /tmp/buildd/linux-2.6-2.6.32/debian/build/source_amd64_none/drivers/scsi/mvsas/mv_sas.c 1669:mvs_abort_task:rc= 5 [ 6384.816020] /tmp/buildd/linux-2.6-2.6.32/debian/build/source_amd64_none/drivers/scsi/mvsas/mv_sas.c 1608:mvs_query_task:rc= 5 [ 6415.804016] /tmp/buildd/linux-2.6-2.6.32/debian/build/source_amd64_none/drivers/scsi/mvsas/mv_sas.c 1669:mvs_abort_task:rc= 5 [ 6415.804021] /tmp/buildd/linux-2.6-2.6.32/debian/build/source_amd64_none/drivers/scsi/mvsas/mv_sas.c 1608:mvs_query_task:rc= 5 [ 6445.816017] /tmp/buildd/linux-2.6-2.6.32/debian/build/source_amd64_none/drivers/scsi/mvsas/mv_sas.c 1669:mvs_abort_task:rc= 5 [ 6445.816022] /tmp/buildd/linux-2.6-2.6.32/debian/build/source_amd64_none/drivers/scsi/mvsas/mv_sas.c 1608:mvs_query_task:rc= 5 [ 6476.804015] /tmp/buildd/linux-2.6-2.6.32/debian/build/source_amd64_none/drivers/scsi/mvsas/mv_sas.c 1669:mvs_abort_task:rc= 5 [ 6476.804020] /tmp/buildd/linux-2.6-2.6.32/debian/build/source_amd64_none/drivers/scsi/mvsas/mv_sas.c 1608:mvs_query_task:rc= 5 So there has definatly changed something with the patch. Further more during the detection of disks during boot I get these messages for almost any SATA disk: 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' If you need more info let me know. Kind regards, Caspar Smit DISCLAIMER: ----------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect. ----------------------------------------------------------------------------------------------------------------------- -- 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
