Bug #4970
closed
[Crunch] Cannot create directory `/tmp/crunch-job/task/compute14.1.keep': File exists
Added by Bryan Cosca over 9 years ago.
Updated over 9 years ago.
Description
qr1hi-8i9sb-wcsmjzy28gz9xf7
...not sure what this error is but I've gotten hit by it twice. even on a job that was supposed to re-run automatically.
- Target version set to Bug Triage
- Subject changed from Cannot create directory `/tmp/crunch-job/task/compute14.1.keep': File exists to [Crunch] Cannot create directory `/tmp/crunch-job/task/compute14.1.keep': File exists
- Category set to Crunch
This looks very related to #4967. In this case, qr1hi-8i9sb-da6mla8d48nd631 was canceled, and the underlying process was killed by signal 9.
The call in question uses mkdir -p. We could still get this error if the path existed and was not a directory. I don't have a good idea about how that might have happened, but it seems like crunch-job should clean its own environment as necessary either way.
This seems to be what mkdir says when you mkdir a stale fuse mount.
tom@alcan:~$ mkdir /tmp/foo
tom@alcan:~$ sshfs zoloft:/foo /tmp/foo
^C
tom@alcan:~$ sshfs zoloft:/foo /tmp/foo
fuse: bad mount point `/tmp/foo': Transport endpoint is not connected
tom@alcan:~$ mkdir -p /tmp/foo
mkdir: cannot create directory ‘/tmp/foo’: File exists
- Target version deleted (
Bug Triage)
- Status changed from New to Resolved
Applied in changeset arvados|commit:ef969ca8dabe571a9866a7b3b7c39098785022fa.
Also available in: Atom
PDF
Updated by Bryan Cosca 
Updated by Tim Pierce 
Updated by 
Updated by