Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

umitools/extract and umitools/dedup are saving extra copies of input files #45

Closed
anoronh4 opened this issue Jun 16, 2023 · 0 comments · Fixed by #46
Closed

umitools/extract and umitools/dedup are saving extra copies of input files #45

anoronh4 opened this issue Jun 16, 2023 · 0 comments · Fixed by #46

Comments

@anoronh4
Copy link
Collaborator

In practice, these two modules are saving extra copies of the input files because of the following nextflow bug: nextflow-io/nextflow#3995

The output channels do not actually contain the input files when the process is complete because by default symlinks are excluded. however, for whatever reason when you are using the scratch directive, all files are copied over regardless of whether they are symlinks or not, which leads to the input files being saved as a hard link, not a soft-link. this leads to unnecessary storage usage, especially because the new file is not a hard link pointing to the original source of the file, but an actual copy with a different inode.

until nextflow fixes this bug we need to make sure the output declaration doesn't match the input files, especially when the inputs are quite large.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant