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

response

Browse source
This commit is contained in:
Joey Hess 2016-11-07 10:56:45 -04:00
parent 1a11ae9da0
commit c8a0e79fb5
No known key found for this signature in database
GPG key ID: C910D9222512E3C7
1 changed files with 24 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

24
doc/forum/What_operations_are_safe_to_interrupt__63__/comment_1_03d8ddc049cf073e5579ca829b352367._comment Normal file
View file

@ -0,0 +1,24 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2016-11-07T14:43:46Z"
content="""
Note that git is not entirely robust against being interrupted.
In particular, interrupting a commit can leave a stale lock file in place,
and committing will then fail until the user manually goes in and removes
the lock file.
I'd say that git-annex is overall more robust against interruptions
than git is, except that git-annex uses git so of course inherits
its limitations.
git-annex tries to handle all interruptions sanely. Ie, files are always
moved into place atomically so partial writes are not a problem, stale lock
files are not a problem, and any recordkeeping that might be lost by an
interruption should be able to be recovered by running the interrupted
command again, or perhaps `git annex fsck`.
The only problem that I can think of with interuptions is that
since git-annex uses temp files in `.git/annex/tmp` extensively,
if it's interrupted nothing will clean up those temp files.
"""]]