From owner-freebsd-fs@FreeBSD.ORG Mon Nov 12 09:56:36 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0222DBD0 for ; Mon, 12 Nov 2012 09:56:35 +0000 (UTC) (envelope-from daniel@digsys.bg) Received: from smtp-sofia.digsys.bg (smtp-sofia.digsys.bg [193.68.3.230]) by mx1.freebsd.org (Postfix) with ESMTP id 31C118FC15 for ; Mon, 12 Nov 2012 09:56:34 +0000 (UTC) Received: from dcave.digsys.bg (dcave.digsys.bg [192.92.129.5]) (authenticated bits=0) by smtp-sofia.digsys.bg (8.14.5/8.14.5) with ESMTP id qAC9uSN5090011 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 12 Nov 2012 11:56:29 +0200 (EET) (envelope-from daniel@digsys.bg) Message-ID: <50A0C7CC.5020108@digsys.bg> Date: Mon, 12 Nov 2012 11:56:28 +0200 From: Daniel Kalchev User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0.10) Gecko/20121029 Thunderbird/10.0.10 MIME-Version: 1.0 To: Steven Hartland Subject: Re: ZFS HBAs + LSI chip sets (Was: ZFS hang (system #2)) References: <1350698905.86715.33.camel@btw.pki2.com> <1350711509.86715.59.camel@btw.pki2.com> <50825598.3070505@FreeBSD.org> <1350744349.88577.10.camel@btw.pki2.com> <1350765093.86715.69.camel@btw.pki2.com> <508322EC.4080700@FreeBSD.org> <1350778257.86715.106.camel@btw.pki2.com> <5084F6D5.5080400@digsys.bg> <50A0ADDA.9040205@digsys.bg> <6E97CF2618534750AE82D23332C6CADC@multiplay.co.uk> In-Reply-To: <6E97CF2618534750AE82D23332C6CADC@multiplay.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Nov 2012 09:56:36 -0000 On 12.11.12 11:18, Steven Hartland wrote: > ----- Original Message ----- From: "Daniel Kalchev" > >> As weird as it sounds, I discovered that my SSD-only zpool (raidz1) >> was using ashift=9. So, changed to ashift=12 and not seen disconnects >> anymore for a week now. Is 4k good for these SSDs? Or 8k is better, >> or larger? >> >> It seems it's really an SSD firmware problem, as the SSDs are likely >> doing more work when used with 512b sectors and from time to time >> fail to communicate properly with the bus. The SSDs are OCZ-VERTEX4 >> (firmware 1.5). >> >> Sometimes it seems to be drive related problem and perhaps the mps >> driver/hardware is too sensitive to drive issues. > > I don't know any SSD or drives for that matter using larger than 4k > sectors. > > Could you post the output from:- > camcontrol identify > > I've got a list of other 4k drives to add quirks for so might as well > include this one while I'm at it :) Quirks, yes. camcontrol identify da0 returns nothing :) camcontrol inquiry da0 returns pass0: Fixed Direct Access SCSI-6 device pass0: Serial Number OCZ-9DS07S644P10JV16 pass0: 600.000MB/s transfers, Command Queueing Enabled smartctl -a /dev/da0 returns more useful info smartctl 6.0 2012-10-10 r3643 [FreeBSD 9.1-PRERELEASE amd64] (local build) Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Indilinx Everest/Martini based SSDs Device Model: OCZ-VERTEX4 Serial Number: OCZ-9DS07S644P10JV16 LU WWN Device Id: 5 e83a97 2e1c46899 Firmware Version: 1.5 User Capacity: 128,035,676,160 bytes [128 GB] Sector Size: 512 bytes logical/physical Rotation Rate: Solid State Device Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2 (minor revision not indicated) SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Mon Nov 12 11:52:32 2012 EET SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 0) seconds. Offline data collection capabilities: (0x1d) SMART execute Offline immediate. No Auto Offline data collection support. Abort Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. No Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x00) Error logging NOT supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 0) minutes. Extended self-test routine recommended polling time: ( 0) minutes. SMART Attributes Data Structure revision number: 18 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x0000 006 000 000 Old_age Offline - 6 3 Spin_Up_Time 0x0000 100 100 000 Old_age Offline - 0 4 Start_Stop_Count 0x0000 100 100 000 Old_age Offline - 0 5 Reallocated_Sector_Ct 0x0000 100 100 000 Old_age Offline - 0 9 Power_On_Hours 0x0000 100 100 000 Old_age Offline - 2323 12 Power_Cycle_Count 0x0000 100 100 000 Old_age Offline - 23 232 Lifetime_Writes 0x0000 100 100 000 Old_age Offline - 101076764290 233 Media_Wearout_Indicator 0x0000 090 000 000 Old_age Offline - 90 SMART Error Log not supported Warning! SMART Self-Test Log Structure error: invalid SMART checksum. SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] Selective Self-tests/Logging not supported Daniel