From owner-freebsd-current@freebsd.org Thu May 26 06:43:05 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 E02F0B4A4A6 for ; Thu, 26 May 2016 06:43:05 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id C1C051E9A for ; Thu, 26 May 2016 06:43:05 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id BCFD3B4A4A5; Thu, 26 May 2016 06:43:05 +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 BC9F7B4A4A4 for ; Thu, 26 May 2016 06:43:05 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (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 51D461E98 for ; Thu, 26 May 2016 06:43:05 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wm0-x233.google.com with SMTP id z87so86420954wmh.0 for ; Wed, 25 May 2016 23:43:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:message-id:reply-to:mime-version :content-transfer-encoding; bh=nPPiAlnryFPSed9aELo8L744udG0N5O4VeYONrKO7Nc=; b=h7fRdf+v5hmMM+AMzpgoYb6qL+zkid7fd+0UXdhDkEigm1y4jyoPeSFtPD0tR8V2yk TiJvtu+pvrhSlTMId7k1bU3TF06pIKNlq/B35ZPi/TqoRnD/bx3GIyNBYhQBo4VyuhNu USvSXGBt8EA+F15daYYSI7pFPbgSQBfh+Pe8XhK/7tgXdv6xU42YjMytzjxvLg7l2zjF uMbPBQBoMOc4mjJT+QFGrF8VX5KKX458uwBsSG+JbVX2tD9BlLFOX5gEewdFPNBSa/gJ igaI+OC78cmAGUjqRr2XMlr3PK1K32RL4lLHTBIo7AtgffYQyaKOqMruE8GWP8cOlNOu 1cTg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:reply-to :mime-version:content-transfer-encoding; bh=nPPiAlnryFPSed9aELo8L744udG0N5O4VeYONrKO7Nc=; b=ZiUDGZSGIbFZuItKlDqgMMLzguh5D6lbfhaZlR9cNOpFjAljP9uBCHVapvDGf9DYXi AP4r6b6k/SsZMQh7hlZOaCJ2fyNHR67ee7pC6XN1L7/X1zqoR3OfqvEij8u3q/avk+GN xVXehHIcwb6HNLRDiYnUQN1RTmJGPeFPntMq82KctHeqYwT7FZ2lci4U94Mi4f9Hrgzo 5I1Wt3MnE4eav/Y2UmZhfOVSfcUM21JPb9rO9Pz4kszNEiOmM1U7v4EYG76vfgbhcU4L Zugwk5V2QDakPabMasGjENQph0N7AUQZjoE7K4TvmPUt6BTrGnrcsyth3B5T2+w0iaex GuDg== X-Gm-Message-State: ALyK8tKi488BTal6EWyeQ5kt8ZnBJ3OJX8w2MaN9Q/zA0S4Mz2Eq2OdwDdptrrx9rHz4/Q== X-Received: by 10.28.142.137 with SMTP id q131mr1751496wmd.81.1464244983841; Wed, 25 May 2016 23:43:03 -0700 (PDT) Received: from ernst.home (p4FC0F647.dip0.t-ipconnect.de. [79.192.246.71]) by smtp.gmail.com with ESMTPSA id 124sm1802396wml.12.2016.05.25.23.43.02 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 25 May 2016 23:43:03 -0700 (PDT) Date: Thu, 26 May 2016 08:42:53 +0200 From: Gary Jennejohn To: current@freebsd.org Subject: Recognizing SMR HDDs Message-ID: <20160526084253.6588938f@ernst.home> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 06:43:06 -0000 Now that ken@ has checked in the SMR code I'm wondering how I can see whether it's having any effect. I have a 8TB SMR disk in a USB3 enclosure. Does the kernel emit any sort of trace to indicate that it sees the drive as SMR and takes that into account? I have the probe trace enabled in my kernel config, but I don't see anything special pop out when I turn the drive on. Does the fact that the drive appears as a /dev/daX play any role? BTW the disk returns an error when multiple LUNs are probed. -- Gary Jennejohn