From owner-freebsd-fs@freebsd.org Sat Mar 31 05:16:15 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 CFA73F5A3FE for ; Sat, 31 Mar 2018 05:16:14 +0000 (UTC) (envelope-from editor@callfortesting.org) Received: from mail-pg0-x22c.google.com (mail-pg0-x22c.google.com [IPv6:2607:f8b0:400e:c05::22c]) (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 4C9CF720BF for ; Sat, 31 Mar 2018 05:16:14 +0000 (UTC) (envelope-from editor@callfortesting.org) Received: by mail-pg0-x22c.google.com with SMTP id t12so6178617pgp.13 for ; Fri, 30 Mar 2018 22:16:14 -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=9wiIW24jfaCWHvT2Ww7yQFOI58Tar4qEO64BYuuNf+c=; b=Y7MotsVQKXUGsIK45uGaIumepvwCaj6pVyWBmE1yiOwtIkap286EBKBYc6hbDzUZpN 2DytAL8yJYzJzzArtreN6+WUz2Ai2LG9FMVSnB5zvAABl1hJa5vH0Dmt97yxAWJED+ih jXwAzZe6TxPcs1MWKcGB76O4ULYo/5lf2UaAbN83MsmvJwkh4D8ixD56lSckUVgZVama D2aGKEkcqJo63X5903k2wfboL97diOlLPGrwSB5O0VReEIg2of+u/TFf1VAT7EUIadhF r5SfU9Ly7B3vMXe53PLA7488xzS1SzKjUbqt8Qmf4VHFNel5p6qW4SRnrYH9rzBYYEa4 qVCQ== 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=9wiIW24jfaCWHvT2Ww7yQFOI58Tar4qEO64BYuuNf+c=; b=pfuSwKf12sEFGY0VtAHQZ1MbORSc0oQC7YOhslwQmE5EbBbXQofpwxZH7AgZFxhaxM 3f9cGBB+yu4KHpgMlmq+lCRdrJa3AF/AYWwLzmWDkdrtK37/4aDc9lApjzb2VpLR1lZ7 +/6bi13QyUvAmzx//EX14+U/6Nz622nqOZrAKLtuUz+J7z8HrHNO+ieKO9BywXMWCmxJ PgSVI+dNAuoEqo4sN+NHtpgJFbKZ3NusairUAGik6iAjqTm6lvwJAit7ZoJRSzFXlUQ+ sDgx+2zPF3/qH4flpHCkEnBP4nwMspY4jR6oyC9hS5VakqIbqX/P+9o4r//PotwrWH43 WN5w== X-Gm-Message-State: AElRT7Fg+4m8JK8QAGS2ZSuNRQU4QzTg83zXktGxIdis+2Eu5nmfa58U rSuHoTUcO6Uz6niouDXe6xuJiGis X-Google-Smtp-Source: AIpwx4/CL0VGyVQP4Igcj+aqDKeIOBb2nvwxFIq/DCtePlJI/C5KJUDPn3BgSYOxtl+ECnj+sfs6bg== X-Received: by 2002:a17:902:8545:: with SMTP id d5-v6mr1795296plo.20.1522473372706; Fri, 30 Mar 2018 22:16:12 -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 z9sm18560016pfg.183.2018.03.30.22.16.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 30 Mar 2018 22:16:11 -0700 (PDT) Subject: Re: smart(8) Call for Testing To: lev@FreeBSD.org, Chuck Tuffli Cc: Tom Evans via freebsd-fs References: <4754cb2f-76bb-a69b-0cf5-eff4d621eb29@callfortesting.org> <1d3f2cef-4c37-782e-7938-e0a2eebc8842@quip.cz> <7ED27465-1BC2-4522-873E-9ECE192EB7A2@ultra-secure.de> From: Michael Dexter Message-ID: <4ac57e03-f5c5-d6f1-d7a8-595398f49015@callfortesting.org> Date: Fri, 30 Mar 2018 22:16:09 -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: 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: Sat, 31 Mar 2018 05:16:15 -0000 On 3/29/18 6:43 AM, Lev Serebryakov wrote: > Monitoring of values and alerting is VERY important (number of > Relocations is main indicator of spinning HDD health and when it raises > it must be known ASAP) Another metric that frequently came up during outreach was any sudden increase in disk latency, usually indicating that you have between one and 24 hours to replace the device. I am curious what people are doing now to determine such changes in latency and where they feel such monitoring should exist in the stack. As for SNMP and friends, I consider those way up the stack with tools like smart(8) simply providing a building block. Michael