Debian hdd spindown - Revision history

T3d: old link was not valid

T3d — Mon, 28 Jun 2010 16:48:18 GMT

old link was not valid

← Older revision		Revision as of 16:48, 28 June 2010
Line 25:		Line 25:
	You can give options to the hdparm command to either view or change specific characteristics. Look through the man page or /etc/hdparm.conf to find out what each option does. For example, changing the spindown time to 5 minutes from the command-line would be:		You can give options to the hdparm command to either view or change specific characteristics. Look through the man page or /etc/hdparm.conf to find out what each option does. For example, changing the spindown time to 5 minutes from the command-line would be:
	hdparm -S60 /dev/hda		hdparm -S60 /dev/hda
-	Read through this [http://www.gentoo-wiki.~~com~~/~~HOWTO_Use_hdparm_to_improve_IDE_device_performance~~ Gentoo ~~wiki~~ page] to find out some good options to play with in order to possibly increase your drive performance. Make sure to run this drive test both '''before''' and '''after''' in order find out whether you changes made things better or worse:	+	Read through this [http://www.gentoo-wiki.info/Hdparm Gentoo Wiki Archives page] to find out some good options to play with in order to possibly increase your drive performance. Make sure to run this drive test both '''before''' and '''after''' in order find out whether you changes made things better or worse:
	hdparm -tT /dev/hda		hdparm -tT /dev/hda

Shubes: clarified alternate location of the SYSLOGD environment variable.

Shubes — Mon, 10 Mar 2008 15:20:29 GMT

clarified alternate location of the SYSLOGD environment variable.

← Older revision		Revision as of 15:20, 10 March 2008
Line 51:		Line 51:
	SYSLOGD="-m 0"		SYSLOGD="-m 0"

		+	If you've upgraded to a more recent version of syslogd, you'll find this parameter in /etc/default/sysklogd instead of the main script.
	''Note: [[User:mflint]] needed to edit '/etc/default/syslogd' instead of '/etc/init.d/sysklogd' in order to stop the MARK log entries.''		''Note: [[User:mflint]] needed to edit '/etc/default/syslogd' instead of '/etc/init.d/sysklogd' in order to stop the MARK log entries.''

Mflint: note about editing /etc/default/syslogd instead

Mflint — Mon, 10 Sep 2007 12:58:43 GMT

note about editing /etc/default/syslogd instead

← Older revision		Revision as of 12:58, 10 September 2007
Line 50:		Line 50:
	edit /etc/init.d/sysklogd and set SYSLOGD to		edit /etc/init.d/sysklogd and set SYSLOGD to
	SYSLOGD="-m 0"		SYSLOGD="-m 0"
		+
		+	''Note: [[User:mflint]] needed to edit '/etc/default/syslogd' instead of '/etc/init.d/sysklogd' in order to stop the MARK log entries.''

	== '''exim''' Configuration ==		== '''exim''' Configuration ==

Ramuk: 17 revision(s)

Ramuk — Thu, 12 Jul 2007 19:44:47 GMT

17 revision(s)

← Older revision

Revision as of 19:44, 12 July 2007

Rosco pc: Reverted edit of XbrGhz, changed back to last version by Christophe

Rosco pc — Fri, 22 Jun 2007 15:18:40 GMT

Reverted edit of XbrGhz, changed back to last version by Christophe

Show changes

XbrGhz at 13:05, 22 June 2007

XbrGhz — Fri, 22 Jun 2007 13:05:43 GMT

Show changes

Christophe at 21:14, 24 April 2007

Christophe — Tue, 24 Apr 2007 21:14:04 GMT

← Older revision		Revision as of 21:14, 24 April 2007
Line 71:		Line 71:

	This is where the mount option noatime comes in. If someone is having trouble getting their drive to spin down, try mounting your filesystem(s) with the noatime (possibly nodiratime as well) to solve this catch.		This is where the mount option noatime comes in. If someone is having trouble getting their drive to spin down, try mounting your filesystem(s) with the noatime (possibly nodiratime as well) to solve this catch.
		+
		+	== '''crontab''' Configuration ==
		+	Check into '''/var/log/syslogd''' file for entries of this kind :
		+	Apr 24 20:17:09 KURO-BOX /USR/SBIN/CRON[1133]: (root) CMD ( run-parts --report /etc/cron.hourly)
		+
		+	If you have some, it means that cron wakes hourly, writing to syslogd and waking up your drive.
		+	To prevent that, provided that you don't need it (check '''into/etc/cron.hourly''' for scripts to be launched hourly) , edit '''/etc/crontab''' and put a # in from of the hourly entry :
		+	#17 * * * * root run-parts --report /etc/cron.hourly
		+
		+	== '''troubleshouting''' ==
		+	Launch the KURO BOX and leave it unused for a long time (e.g. several hours). Then issue the following command (replace YYYY-MM-DD by the current date) to check which log (or other files) have been written during this time (last modified files first) :
		+
		+	ls -ltR /var \| egrep 'var\|YYYY-MM-DD'
		+
		+	Then look into the least recently modified files to see the last entries and try to locate what is responsible for them.

	[[Category: Debian]]		[[Category: Debian]]

Christophe: /* '''exim''' Configuration */

Christophe — Tue, 24 Apr 2007 20:48:11 GMT

'''exim''' Configuration

← Older revision		Revision as of 20:48, 24 April 2007
Line 61:		Line 61:
	0 * * * * mail if [ -x /usr/lib/exim/exim3 -a -f /etc/exim/exim.conf ]; then /usr/lib/exim/exim3 -q ; fi		0 * * * * mail if [ -x /usr/lib/exim/exim3 -a -f /etc/exim/exim.conf ]; then /usr/lib/exim/exim3 -q ; fi
	This will tell cron to start the exim process only on every hour (rather than every 15 minutes or so).		This will tell cron to start the exim process only on every hour (rather than every 15 minutes or so).
		+
		+	'''Alternatively''', if you don't need exim, you can disable it by putting a # at the beginning of the line in '''/etc/cron.d/exim''' :
		+	#08,23,38,53 * * * * mail if [ -x /usr/lib/exim/exim3 -a -f /etc/exim/exim.conf ]; then /usr/lib/exim/exim3 -q ; fi
		+
		+	If you do so, there is no need to run eximconfig.

	== '''sync''' Configuration ==		== '''sync''' Configuration ==

Wikifairy at 17:05, 1 March 2007

Wikifairy — Thu, 01 Mar 2007 17:05:30 GMT

← Older revision		Revision as of 17:05, 1 March 2007
Line 61:		Line 61:
	0 * * * * mail if [ -x /usr/lib/exim/exim3 -a -f /etc/exim/exim.conf ]; then /usr/lib/exim/exim3 -q ; fi		0 * * * * mail if [ -x /usr/lib/exim/exim3 -a -f /etc/exim/exim.conf ]; then /usr/lib/exim/exim3 -q ; fi
	This will tell cron to start the exim process only on every hour (rather than every 15 minutes or so).		This will tell cron to start the exim process only on every hour (rather than every 15 minutes or so).
		+
		+	== '''sync''' Configuration ==
		+	There's one thing that might prevent a spindown, `sync` and atime. Sync runs to flush the file buffer, sync is itself a file so it's atime (last access time) gets updated, which then needs to be written out to disk, repeat. This will either stop your drive from ever spinning down, or will cause it to keep spinning back up when it's otherwise idle.
		+
		+	This is where the mount option noatime comes in. If someone is having trouble getting their drive to spin down, try mounting your filesystem(s) with the noatime (possibly nodiratime as well) to solve this catch.

	[[Category: Debian]]		[[Category: Debian]]

Joshuapurcell: /* Testing */

Joshuapurcell — Sun, 27 Aug 2006 05:47:31 GMT

Testing

← Older revision		Revision as of 05:47, 27 August 2006
Line 25:		Line 25:
	You can give options to the hdparm command to either view or change specific characteristics. Look through the man page or /etc/hdparm.conf to find out what each option does. For example, changing the spindown time to 5 minutes from the command-line would be:		You can give options to the hdparm command to either view or change specific characteristics. Look through the man page or /etc/hdparm.conf to find out what each option does. For example, changing the spindown time to 5 minutes from the command-line would be:
	hdparm -S60 /dev/hda		hdparm -S60 /dev/hda
-	Read through this [http://www.gentoo-wiki.com/HOWTO_Use_hdparm_to_improve_IDE_device_performance Gentoo wiki page] to find out some good options to play with in order to possibly increase your drive performance. Make sure to run this drive test both '''before''' and '''after''' in order find out whether you changes made things better or worse.	+	Read through this [http://www.gentoo-wiki.com/HOWTO_Use_hdparm_to_improve_IDE_device_performance Gentoo wiki page] to find out some good options to play with in order to possibly increase your drive performance. Make sure to run this drive test both '''before''' and '''after''' in order find out whether you changes made things better or worse:
		+	hdparm -tT /dev/hda
		+
	== Configuration ==		== Configuration ==
	Once you have found the best possible settings for your drive, edit the hdparm configuration file:		Once you have found the best possible settings for your drive, edit the hdparm configuration file: