From: SandeepKsinha <sandeepksinha@gmail.com>
To: fscops@googlegroups.com
Cc: linux-fsdevel@vger.kernel.org, john@johnmccutchan.com, rlove@rlove.org
Subject: Re: inotify like service for an entire mount point?
Date: Tue, 4 Aug 2009 00:02:02 +0530 [thread overview]
Message-ID: <37d33d830908031132k826a1b8tee33a11c0b25e8c0@mail.gmail.com> (raw)
In-Reply-To: <87f94c370908030815k292f7b30hc53442eead750534@mail.gmail.com>
Hi Greg,
On Mon, Aug 3, 2009 at 8:45 PM, Greg Freemyer<greg.freemyer@gmail.com> wrote:
>
> 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.
Look for:
int inotifytools_watch_recursively (char const *path, int events) on
http://inotify-tools.sourceforge.net/api/inotifytools_8h.html
>
> So a couple questions:
>
> Can inotify currently be told to monitor an entire mount point?
>
May be the above could help.
> 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?
>
Is the mapping functionality for (inotifytools_watch_recursively)
exported in the kernel.
It would really be great if we hear from the experts.
Kindly suggest. And correct me If I am gone wrong somewhere.
> 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
>
we can specify the mount point
i suppose to watch
11:29 PM
this was the last release
1 January 2008: inotify-tools 3.13 released. Changes:
Fix: `--timefmt' option to inotifywait doesn't work (broken in 3.12)
http://inotify-tools.sourceforge.net/
will it support the new kernel
Regards,
Sandeep.
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google Groups "fscops" group.
> To post to this group, send email to fscops@googlegroups.com
> To unsubscribe from this group, send email to fscops+unsubscribe@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/fscops?hl=en
> -~----------~----~----~----~------~----~------~--~---
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-08-03 18:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-03 15:15 inotify like service for an entire mount point? Greg Freemyer
2009-08-03 18:32 ` SandeepKsinha [this message]
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=37d33d830908031132k826a1b8tee33a11c0b25e8c0@mail.gmail.com \
--to=sandeepksinha@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).