diff options
author | Philipp <Philipp@web> | 2015-01-01 09:47:00 +0000 |
---|---|---|
committer | admin <admin@branchable.com> | 2015-01-01 09:47:00 +0000 |
commit | d1eb8da72098242850618b277b10e02b3ab7e0bf (patch) | |
tree | 8e1fd0d8ba64ae2904f3c78abad884f1102de736 | |
parent | 90f180e0cff9aada03a0af26e82b4ce90bf0c4be (diff) |
-rw-r--r-- | doc/forum/Disadvantages_of_WORM:_long_filename__63__.mdwn | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/forum/Disadvantages_of_WORM:_long_filename__63__.mdwn b/doc/forum/Disadvantages_of_WORM:_long_filename__63__.mdwn new file mode 100644 index 000000000..bff1a3ffe --- /dev/null +++ b/doc/forum/Disadvantages_of_WORM:_long_filename__63__.mdwn @@ -0,0 +1,13 @@ +Hello, + +first, I felt very comfortable with git-annex, but now I run into problems more often, and I think they are related to the WORM backend. I use this backend for my photos, since they are big (25MB) and never modified (camera raws, I don't touch them). So I edited my `.gitattributes` to use `WORM`. + +The problems usually are as follows: I perform an operation, and git (I think it is git which has the problems), and the process exits with exit code 1 and tells me "cannot open binary file: File name too long". The same happens from time to time when I have filenames containing special characters such as ', which can happen when I tag my music collection. I suspect the WORM backend to cause the problems, since the file names in `.git/annex` are indeed very long and ugly beccause of all the escaping done here. + +I am sorry that I cannot give a recipe how to reproduce this behaviour, and sometimes it helps to enter a subdirectory and perform the operation from there, for example: + +`$ git annex copy --to dest Pictures` fails, but `$ cd Pictures/dir_with_problematic_file; git annex copy --to dest .` works. + +Is there some advice or did anyone here observe similar behaviour? + +Best regards, Philipp |