diff options
author | Joey Hess <joeyh@joeyh.name> | 2017-05-11 13:12:51 -0400 |
---|---|---|
committer | Joey Hess <joeyh@joeyh.name> | 2017-05-11 13:12:51 -0400 |
commit | b75462f73a007010277f400b7f91f91b9ea3ade2 (patch) | |
tree | fdb0bcf4bd25b6e32b4524a795dbc47be5dba508 | |
parent | 213c1ff436e39c37337c5c820680dd3b40f8b49a (diff) |
response
-rw-r--r-- | doc/forum/Synchronize_large_files___40__VM_images__41__/comment_3_6488bbe6f39e7154f950530498e9b548._comment | 22 |
1 files changed, 22 insertions, 0 deletions
diff --git a/doc/forum/Synchronize_large_files___40__VM_images__41__/comment_3_6488bbe6f39e7154f950530498e9b548._comment b/doc/forum/Synchronize_large_files___40__VM_images__41__/comment_3_6488bbe6f39e7154f950530498e9b548._comment new file mode 100644 index 000000000..9c55e48f7 --- /dev/null +++ b/doc/forum/Synchronize_large_files___40__VM_images__41__/comment_3_6488bbe6f39e7154f950530498e9b548._comment @@ -0,0 +1,22 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2017-05-11T17:06:23Z" + content=""" +The reason `git annex unlock` is slow is because it makes a copy +of the entire file. The file is left as-is in the annex so the +old version is available later, and the unlocked copy is made available for +modification. + +More recent versions of git-annex support v6 mode, which has a annex.thin +configuration that makes `git annex unlock` not do this copy, so it's very +fast. But then no copy of the old version of the file will be made, +and so you won't be able to revert to the old version. Which seems to be +an important part of your workflow. + +Another way to make `git annex unlock` fast is to use a file system that +supports Copy On Write (CoW). git-annex will use CoW automatically when +available, and then unlocking doesn't need to actually copy the file, +but the old version will still be preserved. Btrfs is the only filesystem +I know of that supports CoW, although there may be others. +"""]] |