public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Padraig Brady <padraig@antefacto.com>
To: Matthias Andree <matthias.andree@stud.uni-dortmund.de>
Cc: Linux-Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Need help tracing regular write activity in 5 s interval
Date: Tue, 04 Jun 2002 12:21:20 +0100	[thread overview]
Message-ID: <3CFCA2B0.4060501@antefacto.com> (raw)
In-Reply-To: <20020602135501.GA2548@merlin.emma.line.org>

Matthias Andree wrote:
> Hello,
> 
> I am using some recent Linux 2.4.x version (2.4.19-pre8-ac5 for now),
> and I have been observing regular disk activity at 5 s intervals for
> some time now which are not related to a particular kernel version.
> 
> I have reiserfs and ext3fs file systems mounted.
> 
> The first thing that came to mind with the "5 s interval" was DJB's
> "svscan", but neither mount -o remount,noatime / nor killall -STOP
> svscan helped.
> 
> The next thing that comes to mind is that journalling file systems
> commit their journal every five seconds. But I have a hard time finding
> out which file system does this or which process causes blocks to be
> marked dirty again. I'd really like to get rid of this regular activity
> unless there's a need.
> 
> So: is there any trace software that can tell me "at 15:52:43.012345,
> process 4321 marked 7 blocks dirty on device /dev/hda5" (or even more
> detail so I can figure if it's just an atime update -- as with svscan --
> or a write access)? And that is NOT to be attached to a specific process
> (hint: strace is not an option).
> 
> Also, I'd like to suggest again a mount option that marks filesystems as
> "clean" automatically after all changes have been committed. This may be
> most useful with "noatime", though.
> 
> Thanks in advance,
> 

This thread may be of interest:
http://marc.theaimsgroup.com/?l=linux-kernel&m=101600745431992&w=2

It's very awkward to analyse things like this at present.
For user -> kernel you could use something like syscalltrack.

As an aside, Nautilus (1.0.4) does stuff every 2 seconds
(checking is there a CD inserted) that causes the disk LED to flash.
The same action also causes the kernel (2.4.13) to fill up the ring
buffer with: "VFS: Disk change detected on device ide1(22,0)".

Padraig.


  reply	other threads:[~2002-06-04 11:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-02 13:55 Need help tracing regular write activity in 5 s interval Matthias Andree
2002-06-04 11:21 ` Padraig Brady [this message]
2002-06-04 11:41   ` Muli Ben-Yehuda
2002-06-04 11:43   ` Xavier Bestel
2002-06-04 12:04   ` Erik Andersen
2002-06-05 14:08     ` Padraig Brady
2002-06-05 15:13       ` Padraig Brady
2002-06-05 15:50       ` Owen Taylor
2002-06-05 16:43         ` Padraig Brady
2002-06-05 22:22           ` Padraig Brady
  -- strict thread matches above, loose matches on Subject: below --
2002-06-02 15:25 Thunder from the hill
2002-06-02 15:41 ` Kevin Krieser
2002-06-02 16:12 ` Kenneth Johansson
2002-06-02 20:19 ` Matthias Andree

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3CFCA2B0.4060501@antefacto.com \
    --to=padraig@antefacto.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthias.andree@stud.uni-dortmund.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox