From: richardj_moore@uk.ibm.com
To: linux-kernel@vger.kernel.org
Subject: Re: who is writing to disk
Date: Fri, 8 Dec 2000 08:29:01 +0000 [thread overview]
Message-ID: <802569AF.002EAD36.00@d06mta06.portsmouth.uk.ibm.com> (raw)
One option, if there's no bespoke mechanism is to use DPorbes and or Linux
Trace Toolkit to set up a trace of file system apis. You could also start
with strace.
Richard Moore - RAS Project Lead - Linux Technology Centre (PISC).
http://oss.software.ibm.com/developerworks/opensource/linux
Office: (+44) (0)1962-817072, Mobile: (+44) (0)7768-298183
IBM UK Ltd, MP135 Galileo Centre, Hursley Park, Winchester, SO21 2JN, UK
Zhiruo Cao <zhiruo@cc.gatech.edu> on 08/12/2000 02:25:03
Please respond to Zhiruo Cao <zhiruo@cc.gatech.edu>
To: linux-kernel@vger.kernel.org
cc: zhiruo@cc.gatech.edu
Subject: who is writing to disk
Hello,
I found a process constantly writing to disk when I run gnome as desktop
and while the whole system is idle. I don't find anything in the log
file, and I don't see anything updated in my home dir or in /tmp. Does it
sound like bdflush is writing? But I don't hear the disk access when I
am not running gnome.
My question then is, is there a (monitoring) tool that can tell me who is
writing to disk? Or how I configure the kernel to know that?
Thanks!
Joe
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-12-08 9:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-08 8:29 richardj_moore [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-12-08 2:25 Zhiruo Cao
2000-12-08 13:50 ` Alan Cox
2000-12-10 11:45 ` Pavel Machek
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=802569AF.002EAD36.00@d06mta06.portsmouth.uk.ibm.com \
--to=richardj_moore@uk.ibm.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®