diff options
| -rw-r--r-- | doc/bugs/Possible_data-loss_if_WORM_keys_do_not_encode_relative_paths/comment_2_e8f011263bfa4c3c3d04494ea1c88523._comment | 21 |
1 files changed, 21 insertions, 0 deletions
diff --git a/doc/bugs/Possible_data-loss_if_WORM_keys_do_not_encode_relative_paths/comment_2_e8f011263bfa4c3c3d04494ea1c88523._comment b/doc/bugs/Possible_data-loss_if_WORM_keys_do_not_encode_relative_paths/comment_2_e8f011263bfa4c3c3d04494ea1c88523._comment new file mode 100644 index 000000000..90684d96c --- /dev/null +++ b/doc/bugs/Possible_data-loss_if_WORM_keys_do_not_encode_relative_paths/comment_2_e8f011263bfa4c3c3d04494ea1c88523._comment @@ -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. + +"""]] |