Quoting Jamie Lokier (jamie@xxxxxxxxxxxxx): > Matt Helsley wrote: > > > That said, if the intent is to allow the restore to be done on > > > another node with a "similar" filesystem (e.g. created by rsync/node > > > image), instead of having a coherent distributed filesystem on all > > > of the nodes then the filename makes sense. > > > > Yes, this is the intent. > > I would worry about programs which are using files which have been > deleted, renamed, or (very common) renamed-over by another process > after being opened, as there's a good chance they will successfully > open the wrong file after c/r, and corrupt state from then on. Userspace is expected to back up and restore the filesystem, for instance using a btrfs snapshot or a simple rsync or tar. If we detect anything which really is not supported (for instance inotify for now) then we fail and leave a log message explaining the failure. thanks, -serge -- 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
