Re: [gentoo-user] reiserfs prevents harddrive suspend of my notebook
Martin Gramatke wrote: Every few seconds something accesses my harddrive, therefore a suspend (hdparm -S1 /dev/hda) is impossible. I have a notebook, so I would really like to spin down the drive for less heat, noise and a longer battery life. 'hdparm -S /dev/hda' does not spin down the drive, it sets a standby timeout for that drive. With no argument, it will likely fail or disable standby for that drive. The -y option forcefully spins down the drive. MAL -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] reiserfs prevents harddrive suspend of my notebook
On Tuesday 15 July 2003 13:15, Martin Gramatke wrote this in an attempt to be witty and informative: > Every few seconds something accesses my harddrive, therefore a > suspend (hdparm -S1 /dev/hda) is impossible. I have a notebook, so I > would really like to spin down the drive for less heat, noise and a > longer battery life. Have you looked at the services you have running? -- Wielder of the mighty +1 LARTsaber of Unsubscribe Instructions At End of Message, the +3 Clue-by-Four of No Attachments to a Mailing List, and the -4 Shield of No Spell Checker http://joseph-a-nagy-jr.homelinux.org http://mc-luug.homelinux.org/ -- [EMAIL PROTECTED] mailing list
RE: [gentoo-user] reiserfs prevents harddrive suspend of my notebook
>Every few seconds something accesses my harddrive, therefore a suspend >(hdparm -S1 /dev/hda) is impossible. I have a notebook, so I >would really >like to spin down the drive for less heat, noise and a longer >battery life. > >I suspect the filesystem reiserfs to do these annoying >accesses. It is a >journaling filessystem and I guess that ext3 would do that >also. Somewhere >I found a tip to mount with noatime, but that didn't help. > >So what are my options? I read about noflushd which reduces >drive access to >a minimum, but only works with ext2. I would prefer to keep >the journaling >file system. Anyone solved that problem? Will reiser4 be better in that >view? I seem to recall that this will happen with fam-oss if you haven't enabled inode monitoring in the kernel. Is this possible? -rex -- [EMAIL PROTECTED] mailing list
