On 6/9/05, Remy Blank <[EMAIL PROTECTED]> wrote:
>
>
> 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
Hi Remy,
I don't know about this. I seem to have gone backwards:
1) If I turn off syslog-ng then it seems that the drive never spinds
up, so I guess at the root it's a syslog-ng issue.
2) When I re-enabled syslog-ng it now started spinning up every 10
minutes, where it used to spin up once an hour.
3) I have edited /etc/syslog-ng/syslog-ng.conf and it does have the
longer time setting:
options {
chain_hostnames(off);
sync(0);
# The default action of syslog-ng 1.6.0 is to log a STATS line
# to the file every 10 minutes. That's pretty ugly after a while.
# Change it to every 12 hours so you get a nice daily update of
# how many messages syslog-ng missed (0).
stats(43200);
};
I'm flummoxed...
I think I'd do jsut as well to put the log file on the MythTV backend
machine and make it mountable as an NFS mount. That just means a bit
of network traffic every 10 minutes, right? I'm planning on placing
the major portion of portage on an NFS mount also so that the frontend
box doesn't carry that file load and I only have to burden the net
with 5 downloads a day. I guess my use of Gentoo has gotten large
enough that I need to start doing stuff like that.
Cheers,
Mark
Jun 9 05:31:29 myth11 vi(6387): dirtied inode 115455 (.viminfo.tmp) on hda3
Jun 9 05:31:29 myth11 vi(6387): dirtied inode 114702 (?) on hda3
Jun 9 05:40:46 myth11 kjournald(869): WRITE block 14947776 on hda3
Jun 9 05:40:46 myth11 kjournald(869): WRITE block 14947784 on hda3
Jun 9 05:40:46 myth11 kjournald(869): WRITE block 1885232 on hda3
Jun 9 05:40:46 myth11 kjournald(869): WRITE block 1885240 on hda3
Jun 9 05:40:50 myth11 kjournald(869): WRITE block 10160 on hda3
Jun 9 05:40:50 myth11 kjournald(869): WRITE block 10168 on hda3
Jun 9 05:40:50 myth11 kjournald(869): WRITE block 10176 on hda3
Jun 9 05:40:50 myth11 kjournald(869): WRITE block 10184 on hda3
Jun 9 05:40:50 myth11 kjournald(869): WRITE block 10192 on hda3
Jun 9 05:40:50 myth11 kjournald(869): WRITE block 10200 on hda3
Jun 9 05:40:50 myth11 kjournald(869): WRITE block 10208 on hda3
Jun 9 05:40:50 myth11 kjournald(869): WRITE block 10216 on hda3
Jun 9 05:40:50 myth11 kjournald(869): WRITE block 10224 on hda3
Jun 9 05:40:50 myth11 kjournald(869): WRITE block 10232 on hda3
Jun 9 05:40:50 myth11 kjournald(869): WRITE block 10240 on hda3
Jun 9 05:40:50 myth11 kjournald(869): WRITE block 10248 on hda3
Jun 9 05:40:50 myth11 kjournald(869): WRITE block 10256 on hda3
Jun 9 05:40:50 myth11 kjournald(869): WRITE block 10264 on hda3
Jun 9 05:40:50 myth11 kjournald(869): WRITE block 10272 on hda3
Jun 9 05:40:52 myth11 pdflush(185): WRITE block 14947784 on hda3
Jun 9 05:40:52 myth11 pdflush(185): WRITE block 0 on hda3
Jun 9 05:40:52 myth11 pdflush(185): WRITE block 8 on hda3
Jun 9 05:40:52 myth11 pdflush(185): WRITE block 1835024 on hda3
Jun 9 05:40:52 myth11 pdflush(185): WRITE block 1835032 on hda3
Jun 9 05:40:52 myth11 pdflush(185): WRITE block 1835040 on hda3
Jun 9 05:40:52 myth11 pdflush(185): WRITE block 1835224 on hda3
Jun 9 05:40:52 myth11 pdflush(185): WRITE block 1851392 on hda3
Jun 9 05:40:52 myth11 pdflush(185): WRITE block 14942208 on hda3
Jun 9 05:40:52 myth11 pdflush(185): WRITE block 14942216 on hda3
Jun 9 05:40:52 myth11 pdflush(185): WRITE block 14942232 on hda3
Jun 9 05:40:52 myth11 pdflush(185): WRITE block 14946512 on hda3
Jun 9 05:40:52 myth11 pdflush(185): WRITE block 14990096 on hda3
Jun 9 05:40:52 myth11 syslog-ng(6377): dirtied inode 936889 (messages) on hda3
Jun 9 05:40:52 myth11 syslog-ng(6377): dirtied inode 936889 (messages) on hda3
Jun 9 05:40:52 myth11 syslog-ng(6377): dirtied inode 936889 (messages) on hda3
Jun 9 05:40:52 myth11 kjournald(869): WRITE block 14947784 on hda3
Jun 9 05:40:52 myth11 kjournald(869): WRITE block 10280 on hda3
Jun 9 05:40:52 myth11 kjournald(869): WRITE block 10288 on hda3
Jun 9 05:40:52 myth11 kjournald(869): WRITE block 10296 on hda3
Jun 9 05:40:52 myth11 pdflush(185): WRITE block 14947784 on hda3
Jun 9 05:40:52 myth11 syslog-ng(6377): dirtied inode 936889 (messages) on hda3
Jun 9 05:40:52 myth11 syslog-ng(6377): dirtied inode 936889 (messages) on hda3
Jun 9 05:40:55 myth11 vi(6388): dirtied inode 933941 (.messages.swp) on hda3
--
gentoo-user@gentoo.org mailing list
