That’s strange, do you have permission to use
/tmp/? Usually that directory is set up to let any user on the machine to write to it. Is it a shared device (perhaps on USB drive or network)?
To change the default path, you can set the
TMPDIR variable in your shell, via
But you shouldn’t need to do that.
Ah, I think I see what must be going on then. QIIME 2 will try to create a hard-link to the file (to save space) as it sees that your original files are on the same disk-device as the tmp directory. However it appears that hard-linking requires write access (which makes sense, you would violate user-permissions otherwise).
We should detect this and fall back to a copy, just like we do if it’s a different device. I’ve created a bug-report to track that. Thanks for helping me diagnose this!
In the meanwhile, you should be able to make a copy of your files (using
cp or similar). This will give you user-write permissions to the data, and QIIME 2 will happily hard-link that to /tmp/ so it can zip it all together in a qza.
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.