From: Anatol Pomozov <anatol.pomozov@gmail.com>
To: Vyacheslav Dubeyko <slava@dubeyko.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: How to implement "filesystem operations tracker"?
Date: Fri, 20 Sep 2013 11:48:29 -0700 [thread overview]
Message-ID: <CAOMFOmWvXTjzxFgetwE7-aKcBWU_3ptGMThtwSUywwE3DpY20Q@mail.gmail.com> (raw)
In-Reply-To: <64A663A1-DEC1-4239-8330-11AFE9681BB7@dubeyko.com>
Hi
On Fri, Sep 20, 2013 at 11:43 AM, Vyacheslav Dubeyko <slava@dubeyko.com> wrote:
>
> On Sep 20, 2013, at 8:39 PM, Anatol Pomozov wrote:
>
>> Hi,
>>
>> I have a following requirement: I start a process that performs a lot
>> of filesystem operations. And I need to know what files my process was
>> using - I need a breakdown by read operations and write operations.
>>
>> A real-world example where such requirement needed is build-systems -
>> I run "gcc foo.c" and I want to know what files are dependencies of
>> this operation. I want to record the information and if any of
>> dependencies is modified - I rerun "gcc" again.
>>
>> There are build systems that track dependencies by mounting by-pass
>> fuse filesystem and chrooting() there. e.g. tup
>> https://github.com/gittup/tup But fuse is relatively slow and it
>> introduces additional buffer copy. I do not want to copy data to
>> user-space and back, all I need is to record what files were
>> stat()/open().
>>
>> Is there a light-weight mechanism that allows to perform it?
>>
>
> What about stackable file system approach (FiST)? As far as I can see,
> this approach is used by UnionFS and eCryptfs. I suppose that such approach
> can be applicable for your task.
Yeah, unionfs looks related. I need somewhat similar but simpler.
I just found wrapfs (http://wrapfs.filesystems.org/) that seems even
closer to what I am looking for. Is wrapfs the best example of "simple
stackable fs"?
next prev parent reply other threads:[~2013-09-20 18:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-20 16:39 How to implement "filesystem operations tracker"? Anatol Pomozov
2013-09-20 16:44 ` Kirill A. Shutemov
2013-09-20 18:00 ` Anatol Pomozov
2013-09-21 0:38 ` Tetsuo Handa
2013-09-20 18:43 ` Vyacheslav Dubeyko
2013-09-20 18:48 ` Anatol Pomozov [this message]
2013-09-20 19:15 ` Vyacheslav Dubeyko
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=CAOMFOmWvXTjzxFgetwE7-aKcBWU_3ptGMThtwSUywwE3DpY20Q@mail.gmail.com \
--to=anatol.pomozov@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=slava@dubeyko.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).