diff options
| author |  Joey Hess <joey@kitenet.net> | 2013-03-11 02:59:44 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2013-03-11 02:59:44 -0400 |
| commit | f2292dc3b494dbed517a48ab2876594f5ace0179 (patch) | |
| tree | cb291b9b2203459af34a3ff7719483aced90390b | |
| parent | a41051e59143824921a7e6e3d60bc2b50881d4b4 (diff) | |
| parent | 1bd61151a2714157431191ced6f6f7fca7b136f9 (diff) | |
Merge branch 'master' of ssh://git-annex.branchable.com
| -rw-r--r-- | doc/bugs/Direct_mode_keeps_re-checksuming_duplicated_files.mdwn | 22 | ||||
| -rw-r--r-- | doc/bugs/Direct_mode_keeps_re-checksuming_duplicated_files/comment_1_cb10385a4f046bfe676720ded3409379._comment | 14 |
2 files changed, 36 insertions, 0 deletions
diff --git a/doc/bugs/Direct_mode_keeps_re-checksuming_duplicated_files.mdwn b/doc/bugs/Direct_mode_keeps_re-checksuming_duplicated_files.mdwn new file mode 100644 index 000000000..845b48a99 --- /dev/null +++ b/doc/bugs/Direct_mode_keeps_re-checksuming_duplicated_files.mdwn @@ -0,0 +1,22 @@ +##What steps will reproduce the problem? + + mkdir test + git init + git annex init "test" + echo "test" > a + echo "test" > b + git annex add a b + git annex sync + git annex direct + git annex sync | grep add + git annex sync | grep add + +##What is the expected output? What do you see instead? + +The last two syncs shouldn't need to add or checksum anything. +Firstly, the output is very confusing because the files have already been added. +Secondly, the sync can take quite a while if you have lots of duplicates or a lot of files that are incidentally similar. + +##What version of git-annex are you using? On what operating system? + +git-annex version: 4.20130227 on Archlinux diff --git a/doc/bugs/Direct_mode_keeps_re-checksuming_duplicated_files/comment_1_cb10385a4f046bfe676720ded3409379._comment b/doc/bugs/Direct_mode_keeps_re-checksuming_duplicated_files/comment_1_cb10385a4f046bfe676720ded3409379._comment new file mode 100644 index 000000000..6a5178bb6 --- /dev/null +++ b/doc/bugs/Direct_mode_keeps_re-checksuming_duplicated_files/comment_1_cb10385a4f046bfe676720ded3409379._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + nickname="joey" + subject="comment 1" + date="2013-03-11T06:31:09Z" + content=""" +It seems that, to fully fix this, direct mode will need to be changed to store multiple inode caches for each key. + +Since the files have the same content, but different inodes and/or mtimes, at least one of them is going to appear changed to sync each time. + +What currently happens is that the first is re-added, and so its inode cache gets stored, and then that means the second's inode cache no longer matches, and it's re-added, and its inode cache gets stored. Putting the inode cache right back in position to force re-adding the first again.. + +Storing multiple inode caches appears easy enough, but I have not yet worked out exactly how to clear out old inode caches. +"""]] |