From owner-freebsd-current@freebsd.org Thu May 26 13:41:23 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 28DAAB4B0C5 for ; Thu, 26 May 2016 13:41:23 +0000 (UTC) (envelope-from ken@kdm.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 134EE1C0F for ; Thu, 26 May 2016 13:41:23 +0000 (UTC) (envelope-from ken@kdm.org) Received: by mailman.ysv.freebsd.org (Postfix) id 128F5B4B0C4; Thu, 26 May 2016 13:41:23 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 122F8B4B0C3 for ; Thu, 26 May 2016 13:41:23 +0000 (UTC) (envelope-from ken@kdm.org) Received: from mithlond.kdm.org (mithlond.kdm.org [96.89.93.250]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "A1-33714", Issuer "A1-33714" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E274D1C0E for ; Thu, 26 May 2016 13:41:22 +0000 (UTC) (envelope-from ken@kdm.org) Received: from mithlond.kdm.org (localhost [127.0.0.1]) by mithlond.kdm.org (8.15.2/8.14.9) with ESMTPS id u4QDfK96003273 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 26 May 2016 09:41:20 -0400 (EDT) (envelope-from ken@mithlond.kdm.org) Received: (from ken@localhost) by mithlond.kdm.org (8.15.2/8.14.9/Submit) id u4QDfKnf003272; Thu, 26 May 2016 09:41:20 -0400 (EDT) (envelope-from ken) Date: Thu, 26 May 2016 09:41:20 -0400 From: "Kenneth D. Merry" To: Gary Jennejohn Cc: current@freebsd.org Subject: Re: Recognizing SMR HDDs Message-ID: <20160526134120.GA3146@mithlond.kdm.org> References: <20160526084253.6588938f@ernst.home> <20160526123445.GA2105@mithlond.kdm.org> <20160526152921.1c91f61a@ernst.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160526152921.1c91f61a@ernst.home> User-Agent: Mutt/1.5.23 (2014-03-12) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (mithlond.kdm.org [127.0.0.1]); Thu, 26 May 2016 09:41:20 -0400 (EDT) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mithlond.kdm.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 May 2016 13:41:23 -0000 On Thu, May 26, 2016 at 15:29:21 +0200, Gary Jennejohn wrote: > On Thu, 26 May 2016 08:34:45 -0400 > "Kenneth D. Merry" wrote: > > > On Thu, May 26, 2016 at 08:42:53 +0200, Gary Jennejohn wrote: > > What kind of drive is it? > > > > ST8000AS 0002-1NA17Z 0X03 Can you send the output of 'camcontrol inquiry daX -v' and 'camcontrol identify daX -v'? There is a quirk for that particular drive to identify it as Drive Managed. When attached behind a SAS controller it looks like this: # camcontrol inquiry da12 -v pass12: Fixed Direct Access SPC-4 SCSI device pass12: Serial Number Z8407Y52 pass12: 600.000MB/s transfers, Command Queueing Enabled > > Here are some things you can do on any disk to see what it is: > > > > diskinfo -v /dev/daX > > > > I don't have the new versions of these utilities installed, so I can't > get any of this neat diskinfo/zonectl information. > > > # sysctl kern.cam.da.19 > > kern.cam.da.19.sort_io_queue: -1 > > kern.cam.da.19.rotating: 1 > > kern.cam.da.19.unmapped_io: 1 > > kern.cam.da.19.error_inject: 0 > > [ begin SMR fields ] > > kern.cam.da.19.max_seq_zones: 0 > > kern.cam.da.19.optimal_nonseq_zones: 0 > > kern.cam.da.19.optimal_seq_zones: 0 > > kern.cam.da.19.zone_support: None > > kern.cam.da.19.zone_mode: Drive Managed > > [ begin SMR fields ] > > kern.cam.da.19.minimum_cmd_size: 6 > > kern.cam.da.19.delete_max: 262144 > > kern.cam.da.19.delete_method: NONE > > > > My drive shows this; > sysctl kern.cam.da.0 > kern.cam.da.0.sort_io_queue: -1 > kern.cam.da.0.rotating: 1 > kern.cam.da.0.unmapped_io: 0 > kern.cam.da.0.error_inject: 0 > kern.cam.da.0.max_seq_zones: 0 > kern.cam.da.0.optimal_nonseq_zones: 0 > kern.cam.da.0.optimal_seq_zones: 0 > kern.cam.da.0.zone_support: None > kern.cam.da.0.zone_mode: Not Zoned <== I guess it can't be managed > kern.cam.da.0.minimum_cmd_size: 10 > kern.cam.da.0.delete_max: 131072 > kern.cam.da.0.delete_method: NONE > > In fact, the ouput for every one of the 4 drives in the enclosure is > the same, even though the other three are non-SMR SATA drives. Yes. There is something slightly odd about the Inquiry data you pasted above. Seagate didn't set the bits in the ATA identify data to mark it as a Drive Managed drive, so I put in a quirk entry to mark it as Drive Managed. Unfortunately with Drive Managed drives that is really all you know. You don't know the zone boundaries or states. But, it is useful to know that you really should write sequentially for good performance. (True of any drive, but especially true with SMR drives.) Ken -- Kenneth Merry ken@FreeBSD.ORG