From: Theodore Tso <tytso@mit.edu>
To: Dave Edwards <ext2@dpe.lusars.net>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Newbie ext2 forensics question...
Date: Fri, 29 Sep 2006 09:37:45 -0400 [thread overview]
Message-ID: <20060929133745.GC5016@thunk.org> (raw)
In-Reply-To: <loom.20060929T063450-383@post.gmane.org>
On Fri, Sep 29, 2006 at 04:47:38AM +0000, Dave Edwards wrote:
> I'm trying to tune a linux system to spin down its (ext2-formatted) disk when
> the system is idle. I've worked down to two problematic applications that
> periodically spin up the disk, even though the (tiny) file they're writing is
> (allegedly) on a tmpfs partition (/tmp/application/datafile, as it happens).
If you are using a distribution that has SystemTap preinstalled,
something that may be simpler to use would be a SystemTap script which
logs which process id's are calling the write system call. Yes,
you'll get false negatives for processes writing to pty's and serial
devices, et. al. If you only have ext3 filesystems on your system,
you can could modify the SystemTap script to print a message including
the pid each time there is a call to ext3_file_write().
(With more advanced SystemTap-foo it would be possible to extract out
the inode information and print the inode #, but you'd have to contact
a SystemTap user's mailing list for help doing something like that.
Still, I suspect getting the process ID is hopefully enough for your
purposes.)
Regards,
- Ted
next prev parent reply other threads:[~2006-09-29 13:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-29 4:47 Newbie ext2 forensics question Dave Edwards
2006-09-29 12:03 ` Peter Kjellström
2006-09-29 13:37 ` Theodore Tso [this message]
2006-09-29 17:24 ` Andreas Dilger
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=20060929133745.GC5016@thunk.org \
--to=tytso@mit.edu \
--cc=ext2@dpe.lusars.net \
--cc=linux-ext4@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