Mark Knecht wrote: > I got back to looking at this item this evening. dmesg is now full of this: > > pdflush(185): WRITE block 14947712 on hda3 > syslog-ng(5341): dirtied inode 936889 (messages) on hda3 > syslog-ng(5341): dirtied inode 936889 (messages) on hda3 > kjournald(869): WRITE block 14947712 on hda3 > kjournald(869): WRITE block 9112 on hda3 > kjournald(869): WRITE block 9120 on hda3 > kjournald(869): WRITE block 9128 on hda3 > pdflush(185): WRITE block 14947712 on hda3 > syslog-ng(5341): dirtied inode 936889 (messages) on hda3 > kjournald(869): WRITE block 9136 on hda3 > kjournald(869): WRITE block 9144 on hda3 > syslog-ng(5341): dirtied inode 936889 (messages) on hda3 > syslog-ng(5341): dirtied inode 936889 (messages) on hda3 > > Is this the logger stuff you were speaking of, or is there a clue here > to what's spinning the drive back up?
Yes, that's it. The kernel is generating a WRITE message, which syslog-ng writes to its log file, which generates a new WRITE message, and so on. You should setup syslog-ng so that WRITE, READ and "dirtied inode" messages are not recorded in your log files, but still printed on the console. The interesting messages are the "dirtied inode" ones, they tell you which processes write data to the disk. kjournald is the journaling process for ext3, it won't trigger if no other process is writing to the disk. Alternatively, you could setup syslog-ng to send the logs to another machine. -- Remy Remove underscore and suffix in reply address for a timely response. -- gentoo-user@gentoo.org mailing list
