On Wed, 2005-06-08 at 07:03 -0700, Mark Knecht wrote: > Thanks Remy. I'll investigate some of these settings. > > As I sat here at 6:48AM (roughly) the drive spun up again. I was > watching 'top' but couldn't tell what process used more CPU.
you can choose to use debug more in laptop mode. #echo 1 > /proc/sys/vm/block_dump and by the way, it should be which process used the HD isn't it? [This is what happens when ppl top post and I don't read the bottom post to reply 1st. So.. I answered the question again. Oh well.. since it's already written] > One setting I noticed rereading the config file was this one: > > <SNIP> > Enable laptop mode always, not just when on battery? > # (This will still disable laptop mode when the battery almost runs out.) > LAPTOP_MODE_ALWAYS_ON=0 > <SNIP> This is just a detection mech. Even though it says it will disable it, I don't think it's really doing that. Because there's no cron-job to check the remaining level etc. > Since it's a desktop machine it would seem that maybe laptop mode is > not totally operational since I would never be on battery? I'm trying > changing this to '1' and seeing what happens. > > cheers, > Mark > > On 6/8/05, Remy Blank <[EMAIL PROTECTED]> wrote: > > Mark Knecht wrote: > > > I'm experimenting with leaving a drive turned off in a MythTV > > > frontend. I have laptop_mode turned on with whatever it has for > > > default settings. I have vixie-cron turned off. Once an hour it seems > > > that the drive still spins up for about 1 minute. How can I find > > > what's causing that and at least make it more infrequent? I see > > > nothing in /var/log/messages nor anything in dmesg. Is there somewhere > > > else I should look? > > > > Laptop mode prevents the drive spinning up when a process writes to the > > disk. However, in its default configuration, it is configured to flush > > the cached writes after a maximum of 600 seconds (MAX_AGE). On my > > laptop, this means that the drive does spin up about every 10 minues. > > > > Your could try enabling "block dumping" in the kernel: > > > > echo 1 >/proc/sys/vm/block_dump > > > > After that, the kernel will dump every block read and write to the > > kernel log. This might allow you to identify which file is accessed and > > which process causes the access. > > > > Note that you better switch off any logger before doing that (or at > > least log through the network), otherwise you'll see all the writes from > > the logger itself... -- Ow Mun Heng Gentoo/Linux on DELL D600 1.4Ghz 1.5GB RAM 98% Microsoft(tm) Free!! Neuromancer 22:25:30 up 10:38, 8 users, load average: 1.35, 1.40, 1.26 -- gentoo-user@gentoo.org mailing list
