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

response

Browse source
This commit is contained in:
Joey Hess 2011-12-06 17:06:08 -04:00
parent adb1dc65bc
commit 6f221f1fc3
1 changed files with 15 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

15
doc/bugs/git-annex_losing_rsync_remotes_with_encryption_enabled.mdwn
View file

@ -1,5 +1,9 @@
Somehow git-annex has again lost a complete rsync remote with encryption enabled... Somehow git-annex has again lost a complete rsync remote with encryption enabled...
> "once again" ? When did it do it before?
> "lost" ? How is the remote lost?
Both *remoteserver* and *localserver* are rsync remotes with enabled encryption. Both *remoteserver* and *localserver* are rsync remotes with enabled encryption.
All commands are executed on the git repository on my laptop. All commands are executed on the git repository on my laptop.
Target of origin is a gitolite repository without annex support (thus the two rsync remotes). Target of origin is a gitolite repository without annex support (thus the two rsync remotes).
@ -38,3 +42,14 @@ I thought that *copy* would verify that, but seems not.
% g a fsck tools % g a fsck tools
fsck tools/md5_sha1_utility.exe (checksum...) ok fsck tools/md5_sha1_utility.exe (checksum...) ok
fsck tools/win32diskimager-RELEASE-0.2-r23-win32.zip (checksum...) ok fsck tools/win32diskimager-RELEASE-0.2-r23-win32.zip (checksum...) ok
> Copy does do an explicit check that the content is present on remoteserver,
> and based on the above, the content was found to be already there,
> which is why it did not copy it again.
>
> Drop does an indentical check that the content is present, and
> since it failed to find it, I am left thinking something must have
> happened to the remove in between the copy and the drop to cause the
> content to go away.
>
> What happens if you copy the data to remoteserver again? --[[Joey]]