Re: atacontrol spindown
All FreeBSD system partitions are on a disk that I never try to spin down. It is weird that something in periodic daily tries to read from my data disks... Alexander. --- On Wed, 4/29/09, Paul B. Mahol wrote: > From: Paul B. Mahol > Subject: Re: atacontrol spindown > To: aopo...@yahoo.com > Cc: freebsd-questions@freebsd.org, "Daniel C. Dowse" > Date: Wednesday, April 29, 2009, 3:17 PM > On 4/29/09, Alexander Popov wrote: > > > > Hi, Paul, > > > > Below is my /etc/crontab. The only thing that is run > at 3 am is periodic > > daily. > > > > If any of scripts from /etc/crontab needs access(just > reading, not > counting writing, > considering it is not already cached) > on spindowned hard disk your mission will fail. > > If you want to keep logging and logs (via another ways) you > could make > memory disk for root > and var slice ... and transfer logs to another media ... > or use another hard disk for that > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: atacontrol spindown
Hi, Daniel, This is the output: Checking setuid files and devices: Checking for uids of 0: root 0 toor 0 Checking for passwordless accounts: Checking login.conf permissions: ***.home kernel log messages: +++ /tmp/security.G4QuXmuU 2009-04-29 03:01:08.0 +0200 +ad4: Idle, spin down +ad4: drive spun down. +ad8: Idle, spin down +ad8: drive spun down. +ad4: request while spun down, starting. +ad8: request while spun down, starting. +ad8: Idle, spin down +ad8: drive spun down. +ad4: Idle, spin down +ad4: drive spun down. +ad4: request while spun down, starting. The timestamps in /var/log/messages suggested that "+ad4: request while spun down, starting." happened at 3:01 am. It would not be very nice if it was due to cron start up; I don't have any system partitions on those drives, it shouldn't touch them... Regards, Alexander. --- On Wed, 4/29/09, Daniel C. Dowse wrote: > From: Daniel C. Dowse > Subject: Re: atacontrol spindown > To: freebsd-questions@freebsd.org > Date: Wednesday, April 29, 2009, 3:07 PM > On Wed, 29 Apr 2009 05:44:51 -0700 (PDT) > Alexander Popov wrote: > > > > > Hi, Daniel, > > > > It must be periodic(8), but I have trouble identifying > what exactly could be the trigger. If I look at > /etc/defaults/periodic.conf, it has > > daily_clean_disks_enable="NO". > > With respect to daily checks, I just have the default > setup, nothing that I added myself. > > > > Are there any other configuration options that I > should look at? > > > > Thanks, > > > > Hi, Alexander, > > maybe post the part for the disk in your output of your > daily security > checks here, would be much easier to find out what the > trigger may be. > > What file/directories are accessed, when it comes to that > point? > > IMHO: i believe it is just because the hdd is > "there", so i think when > the cron runs it just checks that the disk is still there. > > > thx > > D.Dowse > > > -- > The only reality is virtual! > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: atacontrol spindown
Hi, Paul, Below is my /etc/crontab. The only thing that is run at 3 am is periodic daily. # /etc/crontab - root's crontab for FreeBSD # # $FreeBSD: src/etc/crontab,v 1.32.32.1 2008/11/25 02:59:29 kensmith Exp $ # SHELL=/bin/sh PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin HOME=/var/log # #minute hourmdaymonth wdaywho command # */5 * * * * root/usr/libexec/atrun # # Save some entropy so that /dev/random can re-seed on boot. */11* * * * operator /usr/libexec/save-entropy # # Rotate log files every hour, if necessary. 0 * * * * rootnewsyslog # # Perform daily/weekly/monthly maintenance. 1 3 * * * rootperiodic daily 15 4 * * 6 rootperiodic weekly 30 5 1 * * rootperiodic monthly # # Adjust the time zone if the CMOS clock keeps local time, as opposed to # UTC time. See adjkerntz(8) for details. 1,310-5 * * * rootadjkerntz -a --- On Wed, 4/29/09, Paul B. Mahol wrote: > From: Paul B. Mahol > Subject: Re: atacontrol spindown > To: aopo...@yahoo.com > Cc: freebsd-questions@freebsd.org, "Daniel C. Dowse" > Date: Wednesday, April 29, 2009, 2:58 PM > On 4/29/09, Alexander Popov wrote: > > > > Hi, Daniel, > > > > It must be periodic(8), but I have trouble identifying > what exactly could be > > the trigger. If I look at /etc/defaults/periodic.conf, > it has > > daily_clean_disks_enable="NO". > > With respect to daily checks, I just have the default > setup, nothing that I > > added myself. > > > > Are there any other configuration options that I > should look at? > > /etc/crontab > > -- > Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: atacontrol spindown
Hi, Daniel, It must be periodic(8), but I have trouble identifying what exactly could be the trigger. If I look at /etc/defaults/periodic.conf, it has daily_clean_disks_enable="NO". With respect to daily checks, I just have the default setup, nothing that I added myself. Are there any other configuration options that I should look at? Thanks, Alexander. --- On Wed, 4/29/09, Daniel C. Dowse wrote: > From: Daniel C. Dowse > Subject: Re: atacontrol spindown > To: freebsd-questions@freebsd.org > Date: Wednesday, April 29, 2009, 1:50 PM > 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! > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
atacontrol spindown
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? BTW, I am not running smartd daemon, so that cannot be an issue. Thanks in advance, Alexander. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
