On Mon, Apr 08, 2013 at 03:59:49PM +0200, DENIEL Philippe wrote: > On 04/08/13 12:45, Boaz Harrosh wrote: > >From: DENIEL Philippe <philippe.deniel@xxxxxx> > > > >DENIEL Has reported that watching directories through the new fsnotify API, > >might miss some events like deletes and that a directory watch is not recursive, which > >means that we need to open two fd(s) for each directory in the cache. (Which halves our > >fd cache size). > > > >Again from the top of my head, and I know nothing of this subject. > > > >DENIEL please add any information here, so we can talk about it at LSF. > > > What I have seen was this: > - if dnotify() is used, it gets every events. If used on a > directory, it will get every creation and deletion. But it is not > recursive, so we need to use dnotify on every inode we manage. > - if fanotify is used, it is recursive and by using it on the > root of a filesystem, then you have events from the whole underlying > tree. The trouble is that deletion seem not to be caught. > > I do have tests written in C for that. What are you actually using notifications for? If you had adequate leases/delegations, for example, would you still need them? --b. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
