forum/Disadvantages of WORM: long filename?git-annexhttp://git-annex.branchable.com/forum/Disadvantages_of_WORM__58___long_filename__63__/git-annexikiwiki2016-06-02T18:48:45Zcomment 1http://git-annex.branchable.com/forum/Disadvantages_of_WORM__58___long_filename__63__/comment_1_cc5502b55fb71c8fdb235ea9d17216ff/joey2016-03-12T16:58:09Z2015-01-05T16:47:16Z
<p>Please show <code>ls -l</code> output listing one or more of the files with the
problem. Also I'd need to know the filesystem your repository is using
in order to reproduce the problem.</p>
<p>Note that you can use <code>git annex migrate</code> to switch away from the WORM
backend..</p>
comment 2http://git-annex.branchable.com/forum/Disadvantages_of_WORM__58___long_filename__63__/comment_2_d04b7adcc17a305fb1d7f1c1a3641be1/joey2016-06-02T18:48:45Z2015-01-05T17:01:12Z
<p>I refreshed my memory and did some testing, and the WORM backend
deals with extremely large filenames by detecting the filename length
limitations of the filesystem where the repository is located, and if a
WORM key is longer than the maximum filename length, it will truncate it
down to fit.</p>
<p>This avoids any problems in my testing, as long as the WORM keys are being
generated and used all on filesystems with similar filename length limits.
If you are using a version of git-annex older than 4.20131024, it won't
do that, and you should upgrade.</p>
<p>If you are using a mixture of filesystems, eg EXT4 and VFAT, this can still
result in WORM key names generated on EXT4 being too long to fit on the
VFAT filesystem. In this case, I would recommend not using WORM.</p>
<p>Incidentially, that version also made many problematic characters
not be included in WORM key names, so they're more portable to eg, FAT
filesystems.</p>