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 into master

Browse source
This commit is contained in:
Joey Hess 2020-08-26 13:06:14 -04:00
commit 5c1b91f8d3
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 11 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
doc/bugs/annex.hardlink_is_not___34__in_effect__34___in_thin_mode_/comment_3_86e8f44191a004da20db8e97577744a9._comment Normal file
View file

@ -0,0 +1,11 @@
[[!comment format=mdwn
username="yarikoptic"
avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4"
subject="dreaming of everyone using CoW FSs"
date="2020-08-26T01:26:28Z"
content="""
Thank you Joey for looking into it! I only wish that all file systems were CoW so we could quickly \"clone/get\" any amount of data without jeopardizing data as is the case with hardlinks and also that software did not follow symlinks all the way into the .git/annex/objects (which remains the issue even with browsers etc).
But unfortunately it is not the case and that is why we breed all the workarounds to fulfill the use-cases.
For a \"consumer\" who is not intending to modify any of the original hardlinked files -- do you see any other way to get a \"quick\" clone of a heavy in GBs (or TBs) repository without somehow \"marrying\" shared+thin?
May be for data protection there could be some \"read-only-thin\" mode which would make all annexed files read-only (thus in the original and clone) repositories thus making it \"safe\" (somewhat) to have inodes with more than 2 hardlinks?
"""]]