UnifiedGenotyper always give BGZF file has invalid uncompressedLength: -1792842732

Rduque

Hallo,

I running a pipline for exome data. I have 7 exome samples. When the pipeline arrive at the UnifiedGenotyper i always get the error my bam files are malformed.

MESSAGE: SAM/BAM file /tmp/db99fcb54f49eea7ce46ff16a802f7ac/ISDBM261951.recal.bam is malformed: BGZF file has invalid uncompressedLength: -1792842732

All the bam files have are serveral GB big. So I do not get i why the uncompressed length is negative. Here is what is executed:

java -Xmx8g -jar /lib/gatk/GenomeAnalysisTK-2.1-13-g1706365/GenomeAnalysisTK.jar -T UnifiedGenotyper -R /tmp/db99fcb54f49eea7ce46ff16a802f7ac/human_g1k_v37.fasta -nt 30 -glm BOTH -A AlleleBalance -A DepthOfCoverage -A FisherStrand -D /tmp/db99fcb54f49eea7ce46ff16a802f7ac/dbsnp_135.b37.vcf -o samples.variants.raw.vcf -I /tmp/db99fcb54f49eea7ce46ff16a802f7ac/ISDBM261951.recal.bam -I /tmp/db99fcb54f49eea7ce46ff16a802f7ac/ISDBM261953.recal.bam -I /tmp/db99fcb54f49eea7ce46ff16a802f7ac/ISDBM261952.recal.bam -I /tmp/db99fcb54f49eea7ce46ff16a802f7ac/ISDBM261954.recal.bam -I /tmp/db99fcb54f49eea7ce46ff16a802f7ac/ISDBM261950.recal.bam -I /tmp/db99fcb54f49eea7ce46ff16a802f7ac/ISDBM261955.recal.bam -I /tmp/db99fcb54f49eea7ce46ff16a802f7ac/ISDBM261956.recal.bam

Thanks,

Robin

Geraldine_VdAuwera

Hi Robin, it sounds like the previous step is creating corrupted bams. Can you post all the command lines that are used in your pipeline?

Rduque

Hey Geraldine thanks for looking at it.

Meanwhile it is already solved i think(pipeline is still running). I am using an automated pipeline that was generating two times for each sample the same bam. That was a bug. But the index was done only for one of the two, and apparently the bam files generated by the gatk printreads are not the same for same input arguments. They differ some bytes. Cause of the difference between the bam files I was using the wrong index file.

So the generated bams are alright, the error message is just not clear.

Thanks,

Robin

Geraldine_VdAuwera

OK, glad to hear your problem seems to be solved. I'll see if we can improve the error message.