From owner-freebsd-questions@FreeBSD.ORG Wed Apr 29 12:17:35 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 441D0106564A for ; Wed, 29 Apr 2009 12:17:35 +0000 (UTC) (envelope-from dcdowse@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 835528FC18 for ; Wed, 29 Apr 2009 12:17:34 +0000 (UTC) (envelope-from dcdowse@gmx.net) Received: (qmail invoked by alias); 29 Apr 2009 11:50:53 -0000 Received: from p54AA6DC2.dip.t-dialin.net (EHLO ac1dc0de) [84.170.109.194] by mail.gmx.net (mp070) with SMTP; 29 Apr 2009 13:50:53 +0200 X-Authenticated: #30106961 X-Provags-ID: V01U2FsdGVkX18L/7t1YBMLk2AyRMXgkdQ9dPvDHDNRz/aW2W02tx 31FmuHTaF58ns2 Date: Wed, 29 Apr 2009 13:50:52 +0200 From: "Daniel C. Dowse" To: freebsd-questions@freebsd.org Message-Id: <20090429135052.cc870efa.dcdowse@gmx.net> In-Reply-To: <691900.21008.qm@web51406.mail.re2.yahoo.com> References: <691900.21008.qm@web51406.mail.re2.yahoo.com> X-Mailer: Sylpheed 2.6.0 (GTK+ 2.12.11; i386-portbld-freebsd7.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.64 Subject: Re: atacontrol spindown X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Apr 2009 12:17:35 -0000 On Wed, 29 Apr 2009 04:10:04 -0700 (PDT) Alexander Popov wrote: > > Hi, > > With FreeBSD 7.1 I've started using atacontrol spindown for my secondary disks (i.e. disks that are accessed very infrequently). Everything seemed to work nice until I noticed in my "daily security run output" list of kernel messages that suggests that disks get awaken every night at 3 am. Could someone suggest what could trigger my disks to wake up? > Hi Alexander, maybe it is cron when it runs the daily security checks so it checks for the disk? Or have a look at your cronjobs with best regards D. Dowse -- The only reality is virtual!