From owner-freebsd-stable@FreeBSD.ORG Fri Sep 12 08:52:23 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 92F3FA69; Fri, 12 Sep 2014 08:52:23 +0000 (UTC) Received: from smtp1.multiplay.co.uk (smtp1.multiplay.co.uk [85.236.96.35]) by mx1.freebsd.org (Postfix) with ESMTP id 2BC9BFCC; Fri, 12 Sep 2014 08:52:22 +0000 (UTC) Received: by smtp1.multiplay.co.uk (Postfix, from userid 65534) id F3F6420E7088F; Fri, 12 Sep 2014 08:52:21 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.multiplay.co.uk X-Spam-Level: ** X-Spam-Status: No, score=2.2 required=8.0 tests=AWL,BAYES_00,DOS_OE_TO_MX, FSL_HELO_NON_FQDN_1,RDNS_DYNAMIC,STOX_REPLY_TYPE autolearn=no version=3.3.1 Received: from r2d2 (82-69-141-170.dsl.in-addr.zen.co.uk [82.69.141.170]) by smtp1.multiplay.co.uk (Postfix) with ESMTPS id 542F220E7088B; Fri, 12 Sep 2014 08:52:20 +0000 (UTC) Message-ID: From: "Steven Hartland" To: "Willem Jan Withagen" , "Peter Wemm" , References: <540FF3C4.6010305@ish.com.au> <54114029.3060507@FreeBSD.org> <2128347.Ah5i0RTCvp@overcee.wemm.org> <541230F1.3060402@digiware.nl> <5412AED7.9040903@digiware.nl> Subject: Re: getting to 4K disk blocks in ZFS Date: Fri, 12 Sep 2014 09:52:19 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Cc: Andriy Gapon , Aristedes Maniatis X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Sep 2014 08:52:23 -0000 ----- Original Message ----- From: "Willem Jan Withagen" To: "Steven Hartland" ; "Peter Wemm" ; Cc: "Andriy Gapon" ; "Aristedes Maniatis" Sent: Friday, September 12, 2014 9:29 AM Subject: Re: getting to 4K disk blocks in ZFS > On 12-9-2014 10:17, Steven Hartland wrote: >> >> ----- Original Message ----- From: "Willem Jan Withagen" >> >> >>> On 11-9-2014 19:49, Peter Wemm wrote: >>>>> Another downside is 1/4th of uberblocks, 32 vs 128. >>>>> Also, automatic sector size detection works great for me and I've >>>>> never had >>>>> a need to manually tweak ashift. >>>> >>>> Unfortunately, I have. Same drive connected two different ways: >>>> >>>> da12 at mps1 bus 0 scbus1 target 11 lun 0 >>>> da12: Fixed Direct Access SCSI-6 device >>>> da12: 600.000MB/s transfers >>>> da12: Command Queueing enabled >>>> da12: 3815447MB (7814037168 512 byte sectors: 255H 63S/T 486401C) >>>> >>>> ada1 at ahcich1 bus 0 scbus3 target 0 lun 0 >>>> ada1: ATA-8 SATA 3.x device >>>> ada1: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) >>>> ada1: Command Queueing enabled >>>> ada1: 3815447MB (7814037168 512 byte sectors: 16H 63S/T 16383C) >>>> ada1: quirks=0x1<4K> >>>> >>>> The 4k flag is missing when it's on the sas controller. The Ident >>>> strings are changed. >>>> >>>> This came up elsewhere recently. >>> >>> I reported the same fact for the new set of WD REDs I installed. >>> Seems that ada and da have different quirks tables... >>> So disks on SATA connectors on the motherboard are diagnosed as being >>> 4Kb. >>> The disks on my twa don't get the quirk and are considered 512b >> >> LMK the ident strings and I'll look to update the quirks tables. > > Hi Steven, > > Well actually IMHO the quirk tables should be "joined". > Because it is nowadays very simple to get a sata device on a scsi-device > (da??) be it USB, or a controller that make the world look like > /dev/da?? Like the twa I have. > I guess the other way scis devices turning up under ATA would not be common. You can't unfortunately as they report differently as you've found. > That said, it will not be so simple, otherwise somebody(tm) would have > done so already? > > the WD RED under ata: > ada4 at ahcich10 bus 0 scbus11 target 0 lun 0 > ada4: ATA-9 SATA 3.x device > ada4: Serial Number WD-WMC1T4089783 > ada4: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) > ada4: Command Queueing enabled > ada4: 2861588MB (5860533168 512 byte sectors: 16H 63S/T 16383C) > ada4: quirks=0x1<4K> > > under twa > da0 at arcmsr0 bus 0 scbus8 target 0 lun 0 > da0: Fixed Direct Access SCSI-5 device > da0: Serial Number WD-WMC1T4081674 > da0: 250.000MB/s transfers (125.000MHz, offset 32, 16bit) > da0: Command Queueing enabled > da0: 2861588MB (5860533168 512 byte sectors: 255H 63S/T 364801C) > da0: Delete methods: Looks like there are entries which should match already there: { /* WDC Caviar Green Advanced Format (4k) drives */ { T_DIRECT, SIP_MEDIA_FIXED, "ATA", "WDC WD????RX*", "*" }, /*quirks*/DA_Q_4K }, { /* WDC Caviar Green Advanced Format (4k) drives */ { T_DIRECT, SIP_MEDIA_FIXED, "WDC WD??", "??RX*", "*" }, /*quirks*/DA_Q_4K }, What does camcontrol identify and camcontrol inquiry report? Regards Steve