We are using gerrit with jenkins and launching three different jobs for every patchset. When multiple patchsets are uploaded, concurrent jobs are launched. We are using one master and one slave, and sometimes the workspaces get mixed up.

From the build log of the job running on master which had a job #857:

Building on master
Checkout:workspace / /var/lib/jenkins/jobs/project/workspace - hudson.remoting.LocalChannel@bdbd63f
Parsing POMs
Failed to transfer Specified destination directory cannot be created: /home/jenkins-slave1/slave/workspace/project/.repository/org/jboss/arquillian/arquillian-bom/1.0.0.CR5

From the build log of the job running on slave which had a job #858 which was launched at the same time (might not be related, though):
Building remotely on slave1
Checkout:RequesteX_UI_Tests / /home/jenkins-slave1/slave/workspace/project - hudson.remoting.Channel@6a77718e:slave1
Using strategy: Gerrit Trigger
Last Built Revision: Revision 22efd28a79038b66dc840bcd1617d26c6bf3cee2 (refs/changes/09/609/1)
Checkout:RequesteX_UI_Tests / /home/jenkins-slave1/slave/workspace/project - hudson.remoting.LocalChannel@4dce6d48

So the master is trying to use workspace on slave.
I'm not completely sure, but I think that this happens only when jobs are running on different nodes and the jobs are launched at the same time, and the failing job is on the master node.
Full log from master is attached.