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

better followup

Browse source
This commit is contained in:
Joey Hess 2019-09-10 14:43:46 -04:00
parent 154cc1630c
commit d72a8ce8b4
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 23 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

23
doc/forum/Cannot_get_file_from_special_remote/comment_4_6e7252449b3eb9ca5d45b5c3889cacd4._comment Normal file
View file

@ -0,0 +1,23 @@
[[!comment format=mdwn
username="joey"
subject="""comment 4"""
date="2019-09-10T18:36:06Z"
content="""
It seems that the file stored in the remote must have either been deleted
by something, or possibly gotten corrupted. But probably deleted I think,
because a corrupted file would have a different error message.
Lot of possible ways a file could get deleted. Perhaps StorageBox is
storing the files as file on the filesystem, and had a disk problem that
caused fsck to move the file to lost+found. Could happen, disks fail.
Another way would be, if you had made a clone of your git-annex repository,
and enabled StorageBox in there, and done a `git annex move --from
StorageBox`. Then the clone would know it had the copy and StorageBox no
longer did, but until that clone's git-annex branch is pushed out to other
repositories, they will think StorageBox still has the copy, and fail like
you showed.
git-annex fsck exists because of these kinds of situations, and gets things
back to a correct state. But it makes sense to investigate what happened.
"""]]

7
doc/forum/Cannot_get_file_from_special_remote/comment_4_86a1508f5a9ac98e3cbb386cda98d265._comment
View file

@ -1,7 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 4"""
date="2019-09-10T18:33:51Z"
content="""
What does this output? `git annex info StorageBox`
"""]]