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

Reading files from mount can cause cmds to segfault #319

Open
sb10 opened this issue Jul 1, 2020 · 0 comments
Open

Reading files from mount can cause cmds to segfault #319

sb10 opened this issue Jul 1, 2020 · 0 comments
Labels

Comments

@sb10
Copy link
Member

sb10 commented Jul 1, 2020

Is there a muxfys bug around reading?

Running echo "bwa mem -t 25 Homo_sapiens.GRCh38_full_analysis_set_plus_decoy_hla.fa <(zcat CHM1-CHM13-3_S1_L2_R1_001.fastq.gz) <(zcat CHM1-CHM13-3_S1_L2_R2_001.fastq.gz) | samtools sort -O bam -l 0 -T /tmp - | samtools view -T Homo_sapiens.GRCh38_full_analysis_set_plus_decoy_hla.fa -C -o CHM1-CHM13-3_S1_L2.cram -" | ./wr add -o 1 --cpus 25 -m 128G -i mapping -g bwatocram.human -d "samtools.faidx.human,bwa.index.human" --mounts 'ur:/k8s/ref,ur:/k8s/Pond-482886/HJ25L/,cw:/k8s/Pond-482886/HJ25L/crams' --cloud_script sc.sh

[bam_sort_core] merging from 11 files and 1 in-memory blocks...
bash: line 1: 17296 Segmentation fault      (core dumped) bwa mem -t 25 Homo_sapiens.GRCh38_full_analysis_set_plus_decoy_hla.fa <(zcat CHM1-CHM13-3_S1_L2_R1_001.fastq.gz) <(zcat CHM1-CHM13-3_S1_L2_R2_001.fastq.gz)                                                          17297 Done                    | samtools sort -O bam -l 0 -T /tmp -
     17298 Done                    | samtools view -T Homo_sapiens.GRCh38_full_analysis_set_plus_decoy_hla.fa -C -o CHM1-CHM13-3_S1_L2.cram -
 Mount logs:                                                                                                                          t=2018-07-20T15:00:38+0000 lvl=eror msg="fillBuffer read failed" pkg=muxfys mount=/tmp/wr_cwd/b/6/7/a6bdea57c7b44704103c996388cc35296
98790/cwd path=Pond-482886/HJ25L/CHM1-CHM13-3_S1_L2_R1_001.fastq.gz err="unexpected EOF" caller=file.go:187                          t=2018-07-20T15:00:38+0000 lvl=eror msg="Remote call failed" pkg=muxfys mount=/tmp/wr_cwd/b/6/7/a6bdea57c7b44704103c996388cc352969879
0/cwd target=https://cog.sanger.ac.uk/k8s/Pond-482886/HJ25L/ call=Read(Pond-482886/HJ25L/CHM1-CHM13-3_S1_L2_R1_001.fastq.gz) err="unexpected EOF" caller=remote.go:299

Generally, could read failures that only occur when taking a long time to read a file be caused by inodes "expiring" or auto-replacing in my fuse code? I remember something along those lines?...

@sb10 sb10 added the bug label Jul 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant