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

close

Browse source
This commit is contained in:
Joey Hess 2022-06-29 14:37:02 -04:00
parent cddcabfbb5
commit 82063e20c7
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 6 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
doc/bugs/Strange_case_of_data_loss__44___possibly_linked_to_git-annex_with_encrypted_rsync_remote.mdwn
View file

@ -53,3 +53,9 @@ caused this behavior? Or is there any other realistic explanation for this? In
case this is an existing bug, is there any other evidence I can gather? case this is an existing bug, is there any other evidence I can gather?
Needless to say, the lesson here is to run `git annex fsck` regularly even if Needless to say, the lesson here is to run `git annex fsck` regularly even if
you have offsite backups... you have offsite backups...
> My diagnosis is that the file got corrupted before it was copied to disk2
> and disk3. What repository they reached them via does not matter much.
> And indeed, 5 year old git-annex didn't verify the content of
> files it transferred to/from a remote. Current git-annex does, so I guess
> this is [[done]]. --[[Joey]]