Date: Thu, 29 Mar 2018 15:40:16 +0200 From: Ben RUBSON <ben.rubson@gmail.com> To: Chuck Tuffli <chuck@tuffli.net> Cc: lev@freebsd.org, Tom Evans via freebsd-fs <freebsd-fs@freebsd.org> Subject: Re: smart(8) Call for Testing Message-ID: <05EE6839-C5A1-4AF9-A4DC-D01210F715C1@gmail.com> In-Reply-To: <CAM0tzX3RanY=vZbCXTAHB3=kv6aVkuzO5pmwr9g%2BZQoe%2BN1hVg@mail.gmail.com> References: <4754cb2f-76bb-a69b-0cf5-eff4d621eb29@callfortesting.org> <CAMXt9NbdN119RrHnZHOJD1T%2BHNLLpzgkKVStyTm=49dopBMoAQ@mail.gmail.com> <CAM0tzX1oTWTa0Nes11yXg5x4c30MmxdUyT6M1_c4-PWv2%2BQbhw@mail.gmail.com> <CAMXt9NYMrtTNqNSx256mcYsPo48xnsa%2BCCYSoeFLzRsc%2BfQWMw@mail.gmail.com> <CAM0tzX32v2-=saT5iB4WVcsoVOtH%2BXE0OQoP7hEDB1xE%2Bxk%2Bsg@mail.gmail.com> <1d3f2cef-4c37-782e-7938-e0a2eebc8842@quip.cz> <A548BC90-815C-4C66-8E27-9A6F7480741D@bway.net> <7ED27465-1BC2-4522-873E-9ECE192EB7A2@ultra-secure.de> <e54ab9a7-835d-16c7-1fdd-9f8285c0642b@FreeBSD.org> <CAM0tzX3RanY=vZbCXTAHB3=kv6aVkuzO5pmwr9g%2BZQoe%2BN1hVg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 29 Mar 2018 15:27, Chuck Tuffli wrote: > On Wed, Mar 28, 2018 at 11:14 AM, Lev Serebryakov <lev@freebsd.org> wrote: >> On 27.03.2018 22:13, Rainer Duffner wrote: >> >>> Maybe one of the vendors who sells FreeBSD as part of an appliance has >>> shown some interest in this? >>> >>> If you’re hardware is well-defined and thus the output is consistent, I >>> could imagine it’s not too difficult to parse this. >> smartd is very important part of smartmontools, smartctl is not so. >> >> And periodic self-test triggering & check is most important feature of >> smartd, IMHO. >> >> Modern HDDs are liers in SMART. And only regular self-test discover >> real errors on surfaces in my experience. >> >> So, tool without support for HDD self-tests is of little usage for >> appliances, IMHO. > > Thank you for the feedback! As I don't have any experience with > smartd, can you help me better understand which parts of it are most > useful to you? Is it just periodically triggering the self test or > are there other features as well? For example, logging the SMART > values, emailing / triggering notifications when certain criteria are > met, monitoring the self tests, reading the error logs, etc.? This is actually the job of smartd : scheduling / testing / monitoring / alerting :) Ben
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?05EE6839-C5A1-4AF9-A4DC-D01210F715C1>