You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?...
The text was updated successfully, but these errors were encountered:
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
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?...
The text was updated successfully, but these errors were encountered: