From: Kenneth Johansson <ken@canit.se>
To: Thunder from the hill <thunder@ngforever.de>
Cc: Matthias Andree <matthias.andree@stud.uni-dortmund.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Need help tracing regular write activity in 5 s interval
Date: 02 Jun 2002 18:12:08 +0200 [thread overview]
Message-ID: <1023034329.765.16.camel@tiger> (raw)
In-Reply-To: <Pine.LNX.4.44.0206020922410.29405-100000@hawkeye.luckynet.adm>
On Sun, 2002-06-02 at 17:25, Thunder from the hill wrote:
> Hi,
>
> > 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).
>
> Problem: we'd have to do that using printk. printk issues another write
> call, which will mark things dirty. Issued is another printk, which marks
> things dirty and issues another printk...
>
> I suppose one write would become looped here?
Been there done that :)
I turned on debug output for jffs2 without changing klog/syslog to log
to a remote machine. Did not take long for the machine to get unusable.
next prev parent reply other threads:[~2002-06-02 16:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-02 15:25 Need help tracing regular write activity in 5 s interval Thunder from the hill
2002-06-02 15:41 ` Kevin Krieser
2002-06-02 16:12 ` Kenneth Johansson [this message]
2002-06-02 20:19 ` Matthias Andree
-- strict thread matches above, loose matches on Subject: below --
2002-06-02 13:55 Matthias Andree
2002-06-04 11:21 ` Padraig Brady
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
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=1023034329.765.16.camel@tiger \
--to=ken@canit.se \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.andree@stud.uni-dortmund.de \
--cc=thunder@ngforever.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.