mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Added a comment: Possible solution?

Browse source
This commit is contained in:
martin 2014-05-13 17:51:41 +00:00 • committed by admin
parent 606c563138
commit 80704313a4
1 changed files with 16 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

16
doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications/comment_2_349959a6daa722c8350f73feb0b27162._comment Normal file
View file

@ -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...
"""]]