Skip to contentSkip to conversation

FUSE: mnotify (was: [RFC] VFS: mnotify)

RFC Al Boldi 3 participants 3 messages Aug 12, 2007 – Aug 13, 2007 VFS

lore
Share & tools
lore

Al Boldi

author
#0 lore raw
Quoted 7 lines · Al Boldi
Quoted 5 lines · Jakob Oestergaard

Why on earth would you cripple the kernel defaults for ext3 (which is a fine FS for boot/root filesystems), when the *fundamental* problem you really want to solve lie much deeper in the implementation of the filesystem? Noatime doesn't solve the problem, it just makes it "less horrible".

Quoted 8 lines

inotify could easily solve the atime problem, but it's got the drawback of forcing the user to register each and every file/dir of interest, which isn't really reasonable on TB-filesystems.

It could be feasible to introduce mnotify, which would notify the user of meta changes, like atime, across the filesystem. Something like mnotify could also be helpful in CoW situations, provided it supported an in-sync interface.

Here is an idea: Could FUSE be used to produce mnotify behaviour?

Thanks!

--
Al

#1 lore raw
Quoted 11 lines · Al Boldi
Quoted 10 lines · Al Boldi
Quoted 5 lines · Jakob Oestergaard

Why on earth would you cripple the kernel defaults for ext3 (which is a fine FS for boot/root filesystems), when the *fundamental* problem you really want to solve lie much deeper in the implementation of the filesystem? Noatime doesn't solve the problem, it just makes it "less horrible".

inotify could easily solve the atime problem, but it's got the drawback of forcing the user to register each and every file/dir of interest, which isn't really reasonable on TB-filesystems.

What inotify needs is some kind of SUBDIR flag on a watch so that one does not run out of fds, then the TB issue becomes a bit lighter I think.

Quoted 6 lines
Quoted 4 lines

It could be feasible to introduce mnotify, which would notify the user of meta changes, like atime, across the filesystem. Something like mnotify could also be helpful in CoW situations, provided it supported an in-sync interface.

Here is an idea: Could FUSE be used to produce mnotify behaviour?

It may, and in some cases, not. For example, I only had a single filesystem, and would like atime notificatios for it, then how would I do that? What comes to mind is to use a fuse fs that mirrors, but also notifies, ergo:
mount -t fuse.lomount / /mnt
Well, wonderful, now I still need to pivot_root to /mnt, so that all accesses actually end up in fuse-land. And this gets ugly on shutdown, when things have to be unmounted.

Jan

#2 lore raw
Quoted 9 lines · Jan Engelhardt
Quoted 8 lines · Al Boldi
Quoted 7 lines · Al Boldi
Quoted 5 lines · Jakob Oestergaard

Why on earth would you cripple the kernel defaults for ext3 (which is a fine FS for boot/root filesystems), when the *fundamental* problem you really want to solve lie much deeper in the implementation of the filesystem? Noatime doesn't solve the problem, it just makes it "less horrible".

Quoted 7 lines
Quoted 3 lines
Quoted 3 lines

inotify could easily solve the atime problem, but it's got the drawback of forcing the user to register each and every file/dir of interest, which isn't really reasonable on TB-filesystems.

What inotify needs is some kind of SUBDIR flag on a watch so that one does not run out of fds, then the TB issue becomes a bit lighter I think.

There's no risk of running out of fds; inotify only requires one. You still have to register every directory you're interested in, though, but that's a limitation caused by the Unix VFS philosophy and the resulting filesystem design it inspired rather than of inotify itself.

Come up with a filesystem where given an inode you can find every directory that has links to that inode with very little effort, convince everybody to switch from ext3 to this new filesystem, and then maybe inotify could start doing recursive subtree watches. Otherwise, it's just not feasible.

Signature · 1 line
Nicholas Miell <[email protected]>