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

Merge branch 'master' of ssh://git-annex.branchable.com

Browse source
This commit is contained in:
Joey Hess 2021-05-12 15:09:35 -04:00
commit 6eadcab5bf
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 16 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
doc/forum/avoiding_copies_across_mutiple_file_systems/comment_3_43db664a00fb9956ad392b5dc23565ca._comment Normal file
View file

@ -0,0 +1,16 @@
[[!comment format=mdwn
username="https://esgf-node.llnl.gov/esgf-idp/openid/tom_clune"
nickname="tom_clune"
avatar="http://cdn.libravatar.org/avatar/ab2fcb3663856220387ef216fa46d9717513d750fd9ee5a3504c4c7b560ad96e"
subject="comment 3"
date="2021-05-12T16:41:07Z"
content="""
Sorry for the delay in responding. I had a short vacation and jury duty that kept me from responding immediately.
The symlink approach suggested by @Lukey appears to work quite well from my limited testing this far. The git-worktree approach unfortunately required additional write permissions (as noted by @Joey) in the primary repository, and is thus not our preferred approach.
As far as the performance consequences to the symlink option, my tests thus far did not show any obvious performance consequences related to multi-filesystem involvement. Certainly my test repo (~100 files of 50 MB each) seemed to perform quite well, so a real test may effectively require deploying the full data set in this manner.
I had previously tried @Joey's suggestion of symlinking just .git/annex rather than .git/annex/objects. My recollection is that I got error messages, but will test again shortly.
"""]]