[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: HD spindown and fs cache writeback



Hi,
	I am having the same problem that my harddisk does not spindown
	with kernel 2.2.14.

	So how do I try out noflushd? What is the difference between
	noflushd and kflushd?

	thanks for any help in advance.

Shao.

david.gardner@philips.com [david.gardner@philips.com] wrote:
> Ok, having now tried noflushd it seems to do a pretty good job of
> getting the disk on my Sony Vaio C1XE to spin down, and it will
> stay spun down while doing compile cycles on a small test program
> (actually, the whole source to cdparanoia, so not that small):
> while true ; do make clean all <packaging commands> ; done 
> doesn't make the disk spin up.  :-)
> 
> Mobile-update won't work on kernels 2.2.11 and above, as the 
> sys_bdflush call will make it do_exit(0) on first call.  And
> noflushd _requires_ 2.2.11 or above, so noflushd and mobile-update
> will be mutually exclusive.
> 
> Also, I didn't set the noatime option for mount and this all still
> seemed fine.
> 
> Further, to address the spindown of disks when on AC power/battery,
> noflushd will let you have multiple timeouts and send it SIGHUPs,
> so you could use apmcd to detect power changes and send it the 
> required signal to keep things as you want for AC/battery setup.
> 
> 
> </success report>
> 
> 
> 	Dave
> 
> 
> --  
> To UNSUBSCRIBE, email to debian-laptop-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> 

-- 
____________________________________________________________________________
Shao Zhang - Running Debian 2.1  ___ _               _____
Department of Communications    / __| |_  __ _ ___  |_  / |_  __ _ _ _  __ _ 
University of New South Wales   \__ \ ' \/ _` / _ \  / /| ' \/ _` | ' \/ _` |
Sydney, Australia               |___/_||_\__,_\___/ /___|_||_\__,_|_||_\__, |
Email: shao@cia.com.au                                                  |___/ 
_____________________________________________________________________________



Reply to: