Date: Tue, 27 Mar 2018 13:01:28 -0400 From: Charles Sprickman <spork@bway.net> To: Miroslav Lachman <000.fbsd@quip.cz> Cc: Chuck Tuffli <chuck@tuffli.net>, Mark Saad <nonesuch@longcount.org>, freebsd-fs@freebsd.org Subject: Re: smart(8) Call for Testing Message-ID: <A548BC90-815C-4C66-8E27-9A6F7480741D@bway.net> In-Reply-To: <1d3f2cef-4c37-782e-7938-e0a2eebc8842@quip.cz> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Mar 27, 2018, at 12:45 PM, Miroslav Lachman <000.fbsd@quip.cz> wrote: > > Chuck Tuffli wrote on 2018/03/27 16:32: >> On Mon, Mar 26, 2018 at 1:59 PM, Mark Saad <nonesuch@longcount.org> 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”. I have to agree - this is kind of a prior-century tool as far as user friendliness it seems. What is the goal of this tool? The main use for smartmontools seems to be to pluck information about the drive and act on some very specific items (for example, polling the “media wearout indicator” on SSDs is very useful, or read error rates on HDs. But the smartmontools folks seem to spend a fair amount of time with putting drive data in their tool so that meaningful data is presented to the user. Without that level of functionality out of the box, what’s the argument for this being in base vs. being a 3rd party tool that lives in the ports tree? Think of the people that answer mailing list and forum questions when considering adding something like this to base… Again, maybe I’m just missing something or maybe this is here for a particular vendor that needs it or something. Charles > > Maybe I just don't see something... > > Miroslav Lachman > > _______________________________________________ > freebsd-fs@freebsd.org <mailto:freebsd-fs@freebsd.org> mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>; > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org <mailto:freebsd-fs-unsubscribe@freebsd.org>"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A548BC90-815C-4C66-8E27-9A6F7480741D>