So I have an unlocked file which I "--content synced" from my machine 'X03' to my bare-repository remote 'origin'. I edited the same file on another machine 'X02' before syncing, realised that, hit undo and synced with content.
Now the file contains only a "hash-link" as if it was an unlocked file which I did not 'get'. I am afraid that I somehow committed that change, i.e., changing the file content to a single line containing the "hash-link", and deleted the actual file contents. Currently I have no access to 'X03'.
Is there a way to check out an older version or fix this altogether? I assume the real file contents should still be in 'origin'?
It's completely normal for an unlocked file whose content is not locally present to have an annex hash as its content. That is what gets committed to git normally.
@Lukey: thanks for the tip. Will try this at some point with a new repo. For now I just copied the most recent version of the file from /annex/objects/ of my central repo.
@joey: I am afraid I committed the hash-link contents: 'git annex get' didn't change anything. Still I have no idea how this could happen; I'll dig through the history and report back
Like I said, committing the hash link, for an unlocked file, is perfectly normal. And will not result in this behavior.
You need to show command output of commands like git-annex get, git-annex whereis, git-annex fsck for us to understand what the actual problem is.