linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Freemyer <greg.freemyer@gmail.com>
To: linux-fsdevel@vger.kernel.org, fscops@googlegroups.com,
	john@johnmccutchan.com, rlove@rlove.org
Subject: inotify like service for an entire mount point?
Date: Mon, 3 Aug 2009 11:15:38 -0400	[thread overview]
Message-ID: <87f94c370908030815k292f7b30hc53442eead750534@mail.gmail.com> (raw)

John, Robert, others,

I'm working with the ohsm team on a new kernel module and we need a
way as an example to be notified of every file creation event on a
filesystem so we can determine which storage tier a new file should be
allocating data blocks from.

I believe inotify needs a watch item for every directory it is
watching, so in theory we could walk the directory structure somehow
and register every directory with inotify.  That seems like an
excessive amount of overhead for what seems like a simple to implement
need.

So a couple questions:

Can inotify currently be told to monitor an entire mount point?

Would a patch to enable inotify to do so be entertained?  If so, what
about one that added the ability to just the kernel API.  (We have no
need of it in userspace at present.)

Is there an alternate pre-existing linux kernel solution?

Thanks
Greg
-- 
Greg Freemyer
Head of EDD Tape Extraction and Processing team
Litigation Triage Solutions Specialist
http://www.linkedin.com/in/gregfreemyer
Preservation and Forensic processing of Exchange Repositories White Paper -
<http://www.norcrossgroup.com/forms/whitepapers/tng_whitepaper_fpe.html>

The Norcross Group
The Intersection of Evidence & Technology
http://www.norcrossgroup.com

             reply	other threads:[~2009-08-03 15:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-03 15:15 Greg Freemyer [this message]
2009-08-03 18:32 ` inotify like service for an entire mount point? SandeepKsinha

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=87f94c370908030815k292f7b30hc53442eead750534@mail.gmail.com \
    --to=greg.freemyer@gmail.com \
    --cc=fscops@googlegroups.com \
    --cc=john@johnmccutchan.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=rlove@rlove.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;
as well as URLs for NNTP newsgroup(s).