From 06d77132756f0832cafbb69e89ffa3c5b3fcad4a Mon Sep 17 00:00:00 2001 From: martin Date: Tue, 13 May 2014 17:51:41 +0000 Subject: Added a comment: Possible solution? --- .../comment_2_349959a6daa722c8350f73feb0b27162._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications/comment_2_349959a6daa722c8350f73feb0b27162._comment diff --git a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications/comment_2_349959a6daa722c8350f73feb0b27162._comment b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications/comment_2_349959a6daa722c8350f73feb0b27162._comment new file mode 100644 index 000000000..7a78362a3 --- /dev/null +++ b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications/comment_2_349959a6daa722c8350f73feb0b27162._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="martin" + ip="89.183.46.169" + subject="Possible solution?" + date="2014-05-13T17:51:41Z" + content=""" +How about this quick'n dirty vfat compromise: + +For vfat only we do like this (at least for `git annex fsck` command, so that the user doesn't wonder about the strange effects of vfat and can repair this): + +if we have an exact time difference of 1s (probably \"inode problem\") or 1h (\"utc problem\") +we treat this file as likely unmodified and check this via the normal checksum algorithm. + +if checksum is ok, we give a message to the user, that the \"file has only a vfat timestamp problem\" but has correct checksum and if the user decides to do so git annex sets the timestamp in the filesystem to the value from annex' internal tables... + +"""]] -- cgit v1.2.3