From owner-freebsd-fs@freebsd.org Tue Mar 27 19:39:46 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 54F68F52C8B for ; Tue, 27 Mar 2018 19:39:46 +0000 (UTC) (envelope-from editor@callfortesting.org) Received: from mail-pl0-x22e.google.com (mail-pl0-x22e.google.com [IPv6:2607:f8b0:400e:c01::22e]) (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 D46807C59D for ; Tue, 27 Mar 2018 19:39:45 +0000 (UTC) (envelope-from editor@callfortesting.org) Received: by mail-pl0-x22e.google.com with SMTP id x4-v6so37022pln.7 for ; Tue, 27 Mar 2018 12:39:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=callfortesting-org.20150623.gappssmtp.com; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=Miys3jWortPeR50wo1WIJ6CT575VhWr1xnZRCTgT7k0=; b=hlU/ZBHFQEp1dq+Q0Nuqt3uf+6hR82cuwqPos+Hl50QwEvlxhSD78YW/BLOlg2c6df T0klEYClExy9/hv0eu68mPA6kBZRKdgJJCdo4v1gSySlgQhKszVsDrvP52xsj6mjh4Iq 04NuLztRLV8jRE1cNNtdZ9e9weqOeVDbsTHn6aIqQIn0fQ6jWJvCxka6DaPx5WSHGugr zX+rDXDghYvL/kvTM9/vBN9UuwV9FFjHs7Sw5UOoQYt/PnZIsg/DO74YtSQkqdYFkkJV r5UVYn3FcG9Wkaa7lrhd02r6Gt+EoH/BNav7Ki4KDxqygMJjiVjjPrRNllhexhaLowJ2 cFfQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=Miys3jWortPeR50wo1WIJ6CT575VhWr1xnZRCTgT7k0=; b=LYuZW7wAlIu1D7c246LSZpN9jcNXeRTHQJcLyyCFLxlvaNEB0pH7hP8+Xkw2wOHH8o +crWEyFap2DAMogkECI9xsvrd66m8UmTgwey9YfIYTAKD4iYquLhx8aEOzTZA8nX/WW9 7r8ALBafItCFJdud4hunG+jnN01wUHJIVh4ZJW5jDX/Qfs0o5ZJJ/h1BAR8mS5tnmIhD izHpwCu7V19ZyTnDjlu5b1mhUrMvhKb09BAgMQDFmOY0+jkVPJRHOJG27T0rE82W88CJ 28Vpf+0Ab2AUs5HIELMLO0d1G+AENZDpx1NFRt4BLcknWj7TYtnDOuRhBlhvGR9DU7Qo ibJw== X-Gm-Message-State: AElRT7FcRQw5w8fd2jv/Y4L5p56U2HKz5nqpXoEg6jtYyW5QGYJtfb0c AonFQkQCoQqIvTabPRj7G7fGH91H X-Google-Smtp-Source: AIpwx4+AS+tOMxU3VWwKMTFqb3xIFR5wH9iANgRIztV5eSxP8Hnl2wm9AL/UUkYN6H6BXl1VCLsVWw== X-Received: by 2002:a17:902:f24:: with SMTP id 33-v6mr646939ply.242.1522179584924; Tue, 27 Mar 2018 12:39:44 -0700 (PDT) Received: from macbook-2.local (c-67-170-143-17.hsd1.or.comcast.net. [67.170.143.17]) by smtp.gmail.com with ESMTPSA id i86sm4893975pfi.28.2018.03.27.12.39.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 27 Mar 2018 12:39:44 -0700 (PDT) Subject: Re: smart(8) Call for Testing To: Charles Sprickman , Miroslav Lachman <000.fbsd@quip.cz> Cc: freebsd-fs@freebsd.org, Chuck Tuffli References: <4754cb2f-76bb-a69b-0cf5-eff4d621eb29@callfortesting.org> <1d3f2cef-4c37-782e-7938-e0a2eebc8842@quip.cz> From: Michael Dexter Message-ID: Date: Tue, 27 Mar 2018 12:39:43 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Mar 2018 19:39:46 -0000 On 3/27/18 10:01 AM, Charles Sprickman via freebsd-fs wrote: > Again, maybe I’m just missing something or maybe this is here for a particular vendor that needs it or something. You are all welcome to watch the AsiaBSDCon and BSDCan talks on the rationale but here are a few: 1. Ability to use it in-base. Chuck has done the "hard part" and more can be built on top of it. With an in-base utility or library, the installer could check disk health before installation as could zpool(8) (proposed elsewhere with the optimal implementation TBD). 2. Scriptability as per my last post. Most administrators have relatively homogeneous selections of disks and seek four to five key SMART values. 3. Usability. You CAN obtain even raw-er values with a camcontrol inquiry but that truly is a pain and as I recall, they land in hex values, making scripting even more a pain. For what it's worth, I believe smart(8) had NVMe support before smartmontools did. smart(8) is not the work of a vendor but rather is based on my personal experience with hundreds of ZFS-based storage systems in the wild. I made several public calls for input on the design prior to Chuck writing any code. May I kindly request that you rephraise your criticisms as feature requests? Michael