Closed gregdenay closed 2 months ago
What kind of file system are you running this on? Is this on a local drive or network-mounted (NFS, BeeGFS or similar?)
Edit: Make sure you don't have a dangling nextflow process running in the same directory; worst case would be to delete the whole thing (work, results, .nextflow*) and try again.
But it could be that if this is an NFS share or similar, that something "hangs" server-side. Maybe try running the same analysis in a newly created folder to see if the error occurs again.
This is a VM on the server, I guess similar to a local disc?
I tried removing all the work, results and .nextflow folders, restart the server, clean mamba locks and caches and run the wrkflow in a new folder.
I get the same error on older versions of the pipeline too.
Right, so then it is probably not the pipeline (seeing that it used to work previously) but something about the virtual machine and the attached storage (depending on what your setup looks like exactly). Happy to chat offline, but this might be beyond my area of expertise...
This is new:
Any insights? Google is not very helpful