From owner-freebsd-fs@freebsd.org Tue Mar 27 16:46:12 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 42774F69535 for ; Tue, 27 Mar 2018 16:46:12 +0000 (UTC) (envelope-from SRS0=jCOG=GR=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CFEC1710A6 for ; Tue, 27 Mar 2018 16:46:11 +0000 (UTC) (envelope-from SRS0=jCOG=GR=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id E52E828412; Tue, 27 Mar 2018 18:46:03 +0200 (CEST) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id E3FA528422; Tue, 27 Mar 2018 18:45:50 +0200 (CEST) Subject: Re: smart(8) Call for Testing To: Chuck Tuffli , Mark Saad Cc: freebsd-fs@freebsd.org References: <4754cb2f-76bb-a69b-0cf5-eff4d621eb29@callfortesting.org> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <1d3f2cef-4c37-782e-7938-e0a2eebc8842@quip.cz> Date: Tue, 27 Mar 2018 18:45:50 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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 16:46:12 -0000 Chuck Tuffli wrote on 2018/03/27 16:32: > On Mon, Mar 26, 2018 at 1:59 PM, Mark Saad wrote: > ... >> I was thinking more along the lines of when smartctl reports the overall-health >> which is always a good time to read; and very Monty Python-eske >> >> SMART overall-health self-assessment test result: FAILED! >> Drive failure expected in less than 24 hours. SAVE ALL DATA. >> >> https://serverfault.com/questions/114196/smart-warns-me-but-i-dont-trust-it > > This app is different from others in that it only reports the values; > it is up to the user / script / etc. to provide analysis. In the > serverfault example, spin-up time is attribute ID 3. One of my drives > shows: > > $ smart -t da0 | grep "208 3" > 208 3 39 0 100 100 1029 > > smartctl shows it as follows > > $ smartctl -A /dev/da0 > ... > 3 Spin_Up_Time 0x0027 100 100 001 Pre-fail > Always - 1029 > > It would be up to the user or script to decide at what point this > might indicate an imminent failure. What is the purpose of this utility and why it should be in base if almost everyone will need to write something to do the "real job" or "pkg install smartmontools". Maybe I just don't see something... Miroslav Lachman