CA-140596: Failed Lock cannot be garbage collected

I have read the links and I do not think it applies to this case.

1) Comments in code explain purpose while code is implementation. You first say what you wanna do or protect from, then you implement it. So if in the future wants to change the implementation he knows the purpose
2) The link you posted refers to complicated expressions: I do not think
```
e.errno == errno.ENOENT
```
is a complicated expression.
3) The link does not say that comment will rot so use meaningful variables. Meaningful variables are a good practice that does substitute for good comments in the code. There is place for both (https://www.sourceware.org/lvm2/wiki/KernelPatchGuidelines as an example)
4) In this case fileNotFound does not add any other info unless you wanna explain people what ENOENT means (man errno). Moreover it seems even misleading because it seems to suggest that a file is not there: the directory is not there.
What, I think, needs to be explained in a comment is that the containing directory could not be there due to a race condition. This is both the cause for the special handling of ENOENT after a call to open_lockfile and the attempts in rerun.