rework annexed object locking in direct mode & support Windows
Seems that locking of annexed objects when they're being dropped was broken in direct mode: * When taking the lock before dropping, it created the .git/annex/objects file, as an empty file. It seems that the dropping code deleted that, but that is not right, and for all I know could in some situation cause a corrupted object to leak out. * When the lock was checked, it actually tried to open each direct mode file, and checked if it was locked. Not the same lock used above, and could also fail if some consumer of the file locked it. Fixed this, and added windows support by switching direct mode to lock a .lck file.
This commit is contained in:
parent
eefda291c6
commit
721cc0cd22
5 changed files with 92 additions and 32 deletions
2
debian/changelog
vendored
2
debian/changelog
vendored
|
@ -2,6 +2,8 @@ git-annex (5.20140128) UNRELEASED; urgency=medium
|
|||
|
||||
* Windows: It's now safe to run multiple git-annex processes concurrently
|
||||
on Windows; the lock files have been sorted out.
|
||||
* Fixed direct mode annexed content locking code, which is used to
|
||||
guard against recursive file drops.
|
||||
|
||||
-- Joey Hess <joeyh@debian.org> Tue, 28 Jan 2014 13:57:19 -0400
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue