From owner-freebsd-stable@FreeBSD.ORG Mon Oct 27 19:55:04 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 783061065672 for ; Mon, 27 Oct 2008 19:55:04 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 1A3B58FC17 for ; Mon, 27 Oct 2008 19:55:04 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from root by ciao.gmane.org with local (Exim 4.43) id 1KuYB4-00064t-NF for freebsd-stable@freebsd.org; Mon, 27 Oct 2008 19:55:02 +0000 Received: from 200.41.broadband11.iol.cz ([90.178.41.200]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 27 Oct 2008 19:55:02 +0000 Received: from gamato by 200.41.broadband11.iol.cz with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 27 Oct 2008 19:55:02 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: martinko Date: Mon, 27 Oct 2008 20:53:24 +0100 Lines: 64 Message-ID: References: <4905951B.2050602@sh.cvut.cz> <20081027160828.GA24496@icarus.home.lan> <4905F8BB.3080302@sh.cvut.cz> <20081027175337.GA27175@icarus.home.lan> <20081027191028.GA28688@icarus.home.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 200.41.broadband11.iol.cz User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.17) Gecko/20081009 SeaMonkey/1.1.12 In-Reply-To: Sender: news Subject: Re: Short SMART check causes disk op timeouts X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2008 19:55:04 -0000 martinko wrote: > Jeremy Chadwick wrote: >> On Mon, Oct 27, 2008 at 07:52:01PM +0100, martinko wrote: >>> Jeremy Chadwick wrote: >>>>>>> Now, does the timeout cause loss of any data? Is there anything >>>>>>> besides >>>>>>> disabling the testing that I can do about it? >>>>>> Do you understand what short and long offline tests actually do >>>>>> and what >>>>>> they're used for? :-) If so, you'd know that running them >>>>>> periodically >>>>>> is more or less silly (IMHO). >>>>> I do not, not completely :) I think I have just copied the settings >>>>> from >>>>> somewhere and only just tweaked it a bit whenever I have added a disk. >>>> Let me know if you figure out who or what online resource solicited >>>> adding daily short/long tests, as I'd like to talk to them about their >>>> decision. I have a feeling whoever thought it up felt that the tests >>>> were performing entire sector scans of the entire disk, which is simply >>>> not the case. >>>> >>> Hallo, >>> >>> Reading this thread I checked my config to find this: ;-) >>> >>> #/dev/ad0 -a -n standby,q -o on -S on -s (S/../.././02|L/../../7/03) >>> -m root # ++ 2006-11-03 mato >>> /dev/ad0 -a -o on -S on -s (S/../.././02|L/../../7/03) -m root # ++ >>> 2006-11-03 mato >>> >>> I believe I came up with the settings after reading manual page / >>> documentation of the tool. >> >> Can you explain why you're doing this? So far no one's provided a >> reason *why* they're doing short and long offline scans on a daily >> basis. I'm under the impression the conclusion was reached like this: >> "man smartd.conf ... oh, -s, a neat thing, let's enable it". >> >> There are negative repercussions to doing tests of this nature at such >> regular intervals. Once-a-week is borderline acceptable; once a month >> would be quite reasonable. I'd love to know what kind of affect daily >> tests have on MTBF; I can imagine it's reached much sooner with this. >> >> The main point of smartd is to monitor SMART attribute changes. If >> you're concerned about the health of your hard disk, you should be >> looking at your logs and not relying on things like automatic short/long >> tests. Most SMART attributes are updated immediately and not during an >> offline test, and all of those attribute changes will be logged. >> > > You asked Miroslav about source of his configuration. And as it is very ^^^^^^^^ I meant Vaclav, of course, Miroslav's email just arrived. :) > similar to mine I think we both have it from smartd documentation. Where > else to look for information? It's a usual source. So if you think > it's wrong please contact the authors, we're obviously just users. > Thanks. > > M. > > PS: Btw, long offline scan is scheduled on weekly basis, not daily. If > it's good or not I do not know. >