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

Added a comment

Browse source
This commit is contained in:
zardoz 2014-08-16 11:42:22 +00:00 • committed by admin
parent be52dc1b9b
commit c5267cb543
1 changed files with 21 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

21
doc/bugs/Possible_data-loss_if_WORM_keys_do_not_encode_relative_paths/comment_2_e8f011263bfa4c3c3d04494ea1c88523._comment Normal file
View file

@ -0,0 +1,21 @@
[[!comment format=mdwn
username="zardoz"
ip="78.48.163.229"
subject="comment 2"
date="2014-08-16T11:42:22Z"
content="""
Hm, I don’t quite follow the remark on having everything in a single
directory. Rather than saying that the relative path adds additional
entropy, what I was aiming at is the file-system cannot have two
alternate versions of one file name at the same path with the same
mtime, and that’s why it occurred to me that encoding both path and
mtime within the key doesn’t just increase the odds, but effectively
_guarantees_ that there won’t be any collisions. Does this seem to
hold up, or am I missing something? (Of course one can fudge the
mtimes, but that’s something under the user’s control.)
While a large repo with many files very likely has lots of distinct
files with identical basename, mtime (in s.) and size, all these files
with the same mtime must necessarily be located at different paths.
"""]]