From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konstantinos Skarlatos Subject: Re: [PATCH] MVSAS: hot plug handling and IO issues Date: Sun, 14 Mar 2010 15:37:40 +0200 Message-ID: <4B9CE6A4.5030007@gmail.com> References: <6B62480106F2B34D8404CF2FDAA4D9EF71F646BECA@CHN-HCLT-EVS06.HCLT.CORP.HCL.IN> <1267786018.8894.43.camel@mulgrave.site> <6B62480106F2B34D8404CF2FDAA4D9EF71F65D5D21@CHN-HCLT-EVS06.HCLT.CORP.HCL.IN> <4B9CCE61.2070600@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from mail-bw0-f209.google.com ([209.85.218.209]:54397 "EHLO mail-bw0-f209.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756411Ab0CNNhq (ORCPT ); Sun, 14 Mar 2010 09:37:46 -0400 Received: by bwz1 with SMTP id 1so2225760bwz.21 for ; Sun, 14 Mar 2010 06:37:44 -0700 (PDT) In-Reply-To: <4B9CCE61.2070600@gmail.com> Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: "Srinivas Naga Venkatasatya Pasagadugula - ERS, HCL Tech" Cc: James Bottomley , "linux-scsi@vger.kernel.org" On 14/3/2010 1:54 =CE=BC=CE=BC, Konstantinos Skarlatos wrote: > I have installed an AOC-SASLP-MV8 on my system (arch linux amd64=20 > 2.6.33 with latest mvsas patch from Srinivas). I do not have any=20 > mdraid config, every drive has its own filesystem. Everything works=20 > fine, unless i try to boot with 8 disks. Then booting stalls during=20 > the mount disk phase and eventually i get an "unable to read=20 > superblock" message(curiously fscking all the disks seems to work jus= t=20 > before that). When that happens, the blue activity light for the firs= t=20 > drive is constantly on. This also happened with the stock 2.6.33 kern= el. > > With 7 or less disks everything works ok, except for this warning tha= t=20 > does not seem to interfere with the operation of the card. > > ------------[ cut here ]------------ > WARNING: at drivers/ata/libata-core.c:5186 ata_qc_issue+0x31f/0x330=20 > [libata]() > Hardware name: > Modules linked in: ipv6 hwmon_vid xfs exportfs jfs cpufreq_powersave=20 > cpufreq_ondemand fan powernow_k8 freq_table firewire_ohci psmouse=20 > firewire_core edac_core thermal i2c_nforce2 crc_itu_t serio_raw k8tem= p=20 > skge edac_mce_amd button evdev processor pcspkr fuse forcedeth sg=20 > i2c_core rtc_cmos rtc_core rtc_lib ext4 mbcache jbd2 crc16 dm_crypt=20 > dm_mod ohci_hcd sd_mod usb_storage ehci_hcd mvsas libsas sata_sil=20 > scsi_transport_sas pata_amd sata_nv usbcore sata_via ata_generic=20 > pata_via pata_acpi libata scsi_mod > Pid: 2920, comm: hddtemp Not tainted 2.6.33-ARCH #1 > Call Trace: > [] warn_slowpath_common+0x78/0xb0 > [] warn_slowpath_null+0xf/0x20 > [] ata_qc_issue+0x31f/0x330 [libata] > [] ? scsi_init_sgtable+0x4e/0x90 [scsi_mod] > [] ? ata_scsi_pass_thru+0x0/0x2f0 [libata] > [] ata_scsi_translate+0xa6/0x180 [libata] > [] ? scsi_done+0x0/0x20 [scsi_mod] > [] ? scsi_done+0x0/0x20 [scsi_mod] > [] ata_sas_queuecmd+0x139/0x2b0 [libata] > [] sas_queuecommand+0x98/0x300 [libsas] > [] scsi_dispatch_cmd+0xf5/0x230 [scsi_mod] > [] scsi_request_fn+0x322/0x3e0 [scsi_mod] > [] ? lock_timer_base+0x37/0x70 > [] __blk_run_queue+0x5c/0x150 > [] elv_insert+0x140/0x230 > [] __elv_add_request+0x6a/0xc0 > [] blk_execute_rq_nowait+0x60/0xb0 > [] blk_execute_rq+0x81/0xf0 > [] ? blk_rq_map_user+0x198/0x270 > [] sg_io+0x28b/0x3d0 > [] scsi_cmd_ioctl+0x4d0/0x530 > [] ? blkdev_get+0xb/0x10 > [] ? blkdev_open+0x6c/0xc0 > [] ? scsi_ioctl+0x27d/0x390 [scsi_mod] > [] sd_ioctl+0x8f/0xe0 [sd_mod] > [] __blkdev_driver_ioctl+0x8f/0xb0 > [] blkdev_ioctl+0x22e/0x820 > [] block_ioctl+0x37/0x40 > [] vfs_ioctl+0x38/0xd0 > [] do_vfs_ioctl+0x80/0x560 > [] sys_ioctl+0x81/0xa0 > [] system_call_fastpath+0x16/0x1b > ---[ end trace 881aaf5eceedc267 ]--- > > SMART works ok, except for a WD drive that needs a -T permissive to w= ork > (the other WD drive on the controller, a WDC WD15EADS-00P8B0, works=20 > without the -T permissive switch) A small correction here, the WD15EADS-00P8B0 drive is not on the=20 controller but on a motherboard slot, so that explains why smartctl=20 works without -T permissive. The other 6 drives on the SASLP are Seagat= e=20 ST31500541AS and smartctl works without -T permissive for them. > > root ~ # smartctl -a -d ata /dev/sdk > smartctl 5.39.1 2010-01-28 r3054 [x86_64-unknown-linux-gnu] (local bu= ild) > Copyright (C) 2002-10 by Bruce Allen,=20 > http://smartmontools.sourceforge.net > > =3D=3D=3D START OF INFORMATION SECTION =3D=3D=3D > Model Family: Western Digital Caviar Green family > Device Model: WDC WD15EADS-00S2B0 > Serial Number: WD-WCAVY1089106 > Firmware Version: 01.00A01 > User Capacity: 1,500,301,910,016 bytes > Device is: In smartctl database [for details use: -P show] > ATA Version is: 8 > ATA Standard is: Exact ATA specification draft version not indicated > Local Time is: Sun Mar 14 13:39:47 2010 EET > SMART support is: Available - device has SMART capability. > SMART support is: Enabled > > Error SMART Status command failed > Please get assistance from http://smartmontools.sourceforge.net/ > Register values returned from SMART Status command are: > ST =3D0x40 > ERR=3D0x00 > NS =3D0x14 > SC =3D0xa7 > CL =3D0x1f > CH =3D0xf8 > SEL=3D0x40 > A mandatory SMART command failed: exiting. To continue, add one or=20 > more '-T permissive' options. > > I am now stressing the card, reading and writing data at the same tim= e=20 > from every single disk on my system and everything seems to work ok=20 > (fingers crossed). The real test for me will be when I install an HP=20 > SAS expander that i am waiting for any day now. -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html