> For unix:
>
> mtime: The time the file was last modified.
> atime: The time the file was last accessed.
> ctime: The last time _any_ change was made to the file or inode.
>
> All times are to the second.
>
> For VFAT
> mtime: The time the file was last modified (2 second resolution)
> atime: The time the file was last accessed (86400 second resolution)
> ctime: The time the file was _created_ (1ms resolution)
>
> I suppose the unix ctime could be the max of these times.
> I don't think I'd trust it enough to backup incrementally even tho it'd
> pick up the commonest problem of a single mtime; unpacked zip files.
GNUtar's --listed-incremental mode working on a filesystem with unix
semantics covers all the problems including changing owners or permissions
and picking up old files that appear in a new location as a result of
renaming a directory above. If you are doing backups of a live filesystem
you have to live with changes that happen in the current second anyway.
Les Mikesell
les@mcs.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/