[CRIU] [PATCH 0/4] fsnotify: Try to resolve inode path

[Cyrill Gorcunov]

On Tue, Jan 28, 2014 at 10:52:44PM +0400, Pavel Emelyanov wrote:
> We have a problem (https://bugzilla.openvz.org/show_bug.cgi?id=2874):
> some filesystems don't provide open-by-handle functionality and we
> cannot dump (and restore) fsnitifies on them.
> 
> Fortunately, these notifies in typical containers are put in "known"
> locations, so we can try to scan those to resolve the names.
> 
> Yes, it's slow. The ways to make it work better are
> 
> 1) Use openvz's ploop disk for container. In that case fsnotifies
>    will be placed on disk FS's indes, which provide open-by-handle.
> 
> 2) Pre-scan fsnotify-ed inodes on pre-dump and put the cache in
>    image files. The final dump would then get the cache and re-validate
>    it (much faster, than scanning).
> 
> 3) Work on these "some filesystems" (NFS) to provide open-by-handle.
> 
> 
> BTW, this set also fixes the problem when we dump fsnotify, but
> don't restore it. With it we do "can we restore it later" check on
> dump.
> 
> Signed-off-by: Pavel Emelyanov <xemul at parallels.com>

Looks good to me, thanks Pavel!

Acked-by: Cyrill Gorcunov <gorcunov at openvz.org>