From owner-freebsd-current@freebsd.org Thu May 26 14:03:06 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 5DB22B4B677 for ; Thu, 26 May 2016 14:03:06 +0000 (UTC) (envelope-from mozolevsky@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 3DF271CF1 for ; Thu, 26 May 2016 14:03:06 +0000 (UTC) (envelope-from mozolevsky@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 3D432B4B676; Thu, 26 May 2016 14:03:06 +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 3CC64B4B675 for ; Thu, 26 May 2016 14:03:06 +0000 (UTC) (envelope-from mozolevsky@gmail.com) Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C9F991CF0; Thu, 26 May 2016 14:03:05 +0000 (UTC) (envelope-from mozolevsky@gmail.com) Received: by mail-wm0-x231.google.com with SMTP id n129so228790519wmn.1; Thu, 26 May 2016 07:03:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=fGE0MT/fAtFGrckbH6h2OITnl1xwikfzv+dk6EarcL4=; b=wvcjUaJn0jtn50THlyRswbeSJ7nJv6eBClCVsIWXwpvr/NxGfak2NCS2CtJFlYqe1G aJk1piSJo4cyhKBiuHDgi0O/bqFbUNEIRmb+kCnGLxaUFH/3t835+citZAqmRFF8dpT9 VnsMbOYX4TIhBT/YGUVdp9MVjdPhvHBQiyJ1glJcbTluo7RTu/6uHFbfHqmCJLw2jeGk n87H4Qfv6jxcGk/v6sMhSlF9h+/KzgkWlnXrRSEVclJH1MFbTPFU0eYNovJ4xVErqFdx GgTkWqn2RIcsP3fn5VH4MK+mwgRqATyTAVnsEt1AOlgqkpIpwsvffHP9+r1horEIWtBB 5o5g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=fGE0MT/fAtFGrckbH6h2OITnl1xwikfzv+dk6EarcL4=; b=YYRUxLp9e53D++H4JAuRCLYNC6eddAeOuaaw6Kj9Q8pGDy/hXcc/bKGefws1qfF8BL 8al40s0E2xwLbR7C12t9b6DMyHRp8pTF4vGnjpool9Ey/b6abio2QzYBtMWbUGql1uUz 1s3tXCE8hl76iCi9/KgxstpIrBR3KBbKEsm+/vsryvNd3ODrO8KxldW6xV6j6pfC9Fhw XW0m2bVLjCFRoZpDlevm3OP0aeLkziS/EfSVjZRWzbFFlUDbtjNwJKc0VVAgwyG4JmeZ vYyrnQvWDZKcAYXrwbvgz7LVuC9nLDL/tYoWzUdQoNRPf3IX8xMxB9bBKECJi/RaCmi/ g4cw== X-Gm-Message-State: ALyK8tITr9nHMSpZgymmnNhcVZUwmXeyMyM5I6H6nYsgG+JZYt7sQ9mBiVu0C0WuKRe8/xLA2hun4oawAgoWXg== X-Received: by 10.28.52.75 with SMTP id b72mr3926917wma.98.1464271384344; Thu, 26 May 2016 07:03:04 -0700 (PDT) MIME-Version: 1.0 Sender: mozolevsky@gmail.com Received: by 10.28.29.80 with HTTP; Thu, 26 May 2016 07:02:24 -0700 (PDT) In-Reply-To: <20160526134120.GA3146@mithlond.kdm.org> References: <20160526084253.6588938f@ernst.home> <20160526123445.GA2105@mithlond.kdm.org> <20160526152921.1c91f61a@ernst.home> <20160526134120.GA3146@mithlond.kdm.org> From: Igor Mozolevsky Date: Thu, 26 May 2016 15:02:24 +0100 X-Google-Sender-Auth: HsOa4kuCfGN_f0vr_LAgUT3IeWE Message-ID: Subject: Re: Recognizing SMR HDDs To: "Kenneth D. Merry" Cc: Gary Jennejohn , current Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 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 14:03:06 -0000 On 26 May 2016 at 14:41, Kenneth D. Merry wrote: > 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 > [snip] > 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.) > The drive is supposed to have Word 69 set to 0x0001 and support ZAC MGMT IN/OUT - http://www.seagate.com/www-content/product-content/hdd-fam/seagate-archive-hdd/en-us/docs/100795782a.pdf at pg. 24 and 28. Incidentally AR17 firmware is a new batch, perhaps Seagate did what they did with -DL003 drives where the early models reported 512n sector size (so as not to confuse computers) and the later models properly reported 4kn sector size? -- Igor M.