From: Dave Chinner <david@fromorbit.com>
To: Sushil Mantri <sushilmantri@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: A stackable filesystem to trace low level filesystem operations
Date: Wed, 4 Jan 2012 11:03:14 +1100 [thread overview]
Message-ID: <20120104000314.GV23662@dastard> (raw)
In-Reply-To: <CAFFtA8429YabMVLp-f15GXBknK+W2oMpqYkZT42zLFaSJ-RBVA@mail.gmail.com>
On Tue, Jan 03, 2012 at 04:20:21PM -0500, Sushil Mantri wrote:
> Hi All,
>
> Sorry but this isn't a ext4 specific question but a general filesystem question.
>
> I am looking for a way to track filesystem level operation like
> operation(read/write), filename, offset, size of read/write, pid of
> the requesting process. The goal of my project is to collect such
> traces and understand access usage of directories and more. I would
> like to filter other operation like open,close, etc and requests to
> procfs, etc. There was a stackable file system earlier called Tracefs.
> It isn't supported anymore though. The original paper can be found
> here: filesystems.org/docs/tracefs-fast04/tracefs.ps
Add your own trace points to the VFS and extract and filter them
with trace-cmd.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2012-01-04 0:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 21:20 A stackable filesystem to trace low level filesystem operations Sushil Mantri
2012-01-03 21:45 ` Greg Freemyer
2012-01-03 21:50 ` Sushil Mantri
2012-01-03 22:53 ` Greg Freemyer
2012-01-04 0:03 ` Dave Chinner [this message]
2012-01-04 1:37 ` Theodore Tso
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=20120104000314.GV23662@dastard \
--to=david@fromorbit.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sushilmantri@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).