diff options
| author |  martin <martin@web> | 2014-05-05 15:31:48 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2014-05-05 15:31:48 +0000 |
| commit | f807e25a9d9c3a2be8c7072fcca2156b76237cae (patch) | |
| tree | 633810e57c137dfd11484c7c3362a46a3e176144 /doc | |
| parent | 7aa6a265211cd14f8652e071fa53e93bbf08061a (diff) | |
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn index 9255749f5..5ede475d2 100644 --- a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn +++ b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn @@ -1,4 +1,4 @@ -The Date resolution for FAT is only 2 seconds for the "last modified time." +The Date resolution of the FAT filesystem is only 2 seconds for the "last modified time." This leads to the strange behaviour, that after umount and remount of an usb drive (direct mode) git-annex thinks that suddenly approx. 50% of the files are modified. (after remount the times appears to be rounded to even values - the inode cache before unmount had 1 second resolution) So git-annex is not real "guilty" but it would be fine to create a "workaround" for this problem... |