From 219de02f452d7c421caa91a4728d97f287a2de11 Mon Sep 17 00:00:00 2001 From: erewhon Date: Wed, 10 Oct 2018 15:59:06 +0000 Subject: [PATCH] --- .../Unlocking_files_gives_symlink_content.mdwn | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/forum/Unlocking_files_gives_symlink_content.mdwn diff --git a/doc/forum/Unlocking_files_gives_symlink_content.mdwn b/doc/forum/Unlocking_files_gives_symlink_content.mdwn new file mode 100644 index 0000000000..ad7d435147 --- /dev/null +++ b/doc/forum/Unlocking_files_gives_symlink_content.mdwn @@ -0,0 +1,16 @@ +I am just beginning to use git-annex so it is possible that the following issue was caused by my own mishap. It cropped after commiting a number of file renames. + +When files are locked, I am able to view their contents. However, when I unlock certain files, their contents appear to be replaced by the contents of the symlink. Locking them again allows me to view their contents. For instance, with one unlocked file, say `test.md`, I get + +``` +$ cat test.md +/annex/objects/SHA256E-s535--d37feb3390801b601a9cee77f6467f01aaabbb293149d20d75df26172a3594fd.md +``` + +Some files still behave as expected. + +My git-annex repo is in my Linux home folder on an ext4 partition so handling symlinks should not be an issue. + +I did have a look at [this discussion](https://git-annex.branchable.com/forum/git_annex_file_content_replaced_with_symlink_content/) but none of the solutions there seemed to do the trick. + +Any help is much appreciated.