[ERROR] Input bam file was read incompletely during peak calling

[guodong1988]

When I use macs3 callpeak tool to call peaks by using my bam file, I found only small part of the bam file was read without any warnings or errors, would you please help me to solve the problem? Thank you so much.
My system is MacOS12.6
Bam file:
https://drive.google.com/file/d/1QF0YCSz_u3_iUu8tzLE6h5FO4rhhcZFK/view?usp=share_link
My Code:
macs3 callpeak -B -f BAMPE -t H3K4me3_WT.sorted.bam -g mm -p 0.05 --broad --outdir ./MACS/H3K4me3_KO_vs_WT -n H3K4me3_WT --nomodel --extsize 147

log:
INFO @ 11 Aug 2023 11:53:21: [28 MB]
'# Command line: callpeak -B -f BAMPE -t H3K4me3_WT.sorted.bam -g mm -p 0.05 --broad --outdir ./MACS/H3K4me3_KO_vs_WT -n H3K4me3_WT --nomodel --extsize 147
'# ARGUMENTS LIST:
'# name = H3K4me3_WT
'# format = BAMPE
'# ChIP-seq file = ['H3K4me3_WT.sorted.bam']
'# control file = None
'# effective genome size = 2.65e+09
'# band width = 300
'# model fold = [5, 50]
'# pvalue cutoff for narrow/strong regions = 5.00e-02
'# pvalue cutoff for broad/weak regions = 1.00e-01
'# qvalue will not be calculated and reported as -1 in the final output.
'# The maximum gap between significant sites is assigned as the read length/tag size.
'# The minimum length of peaks is assigned as the predicted fragment length "d".
'# Larger dataset will be scaled towards smaller dataset.
'# Range for calculating regional lambda is: 10000 bps
'# Broad region calling is on
'# Paired-End mode is on

INFO @ 11 Aug 2023 11:53:21: [28 MB] #1 read fragment files...
INFO @ 11 Aug 2023 11:53:21: [28 MB] #1 read treatment fragments...
INFO @ 11 Aug 2023 11:54:16: [68 MB] 17395 fragments have been read.
INFO @ 11 Aug 2023 11:54:16: [68 MB] #1 mean fragment size is determined as 315.3 bp from treatment
INFO @ 11 Aug 2023 11:54:16: [68 MB] #1 fragment size = 315.3
INFO @ 11 Aug 2023 11:54:16: [68 MB] #1 total fragments in treatment: 17395
INFO @ 11 Aug 2023 11:54:16: [68 MB] #1 user defined the maximum fragments...
INFO @ 11 Aug 2023 11:54:16: [68 MB] #1 filter out redundant fragments by allowing at most 1 identical fragment(s)
INFO @ 11 Aug 2023 11:54:16: [68 MB] #1 fragments after filtering in treatment: 12219
INFO @ 11 Aug 2023 11:54:16: [68 MB] #1 Redundant rate of treatment: 0.30
INFO @ 11 Aug 2023 11:54:16: [68 MB] #1 finished!
INFO @ 11 Aug 2023 11:54:16: [68 MB] #2 Build Peak Model...
INFO @ 11 Aug 2023 11:54:16: [68 MB] #2 Skipped...
INFO @ 11 Aug 2023 11:54:16: [68 MB] #3 Call peaks...
INFO @ 11 Aug 2023 11:54:16: [68 MB] #3 Call broad peaks with given level1 -log10pvalue cutoff and level2: 1.30103, 1.00000...
INFO @ 11 Aug 2023 11:54:16: [68 MB] #3 Pre-compute pvalue-qvalue table...
INFO @ 11 Aug 2023 11:54:16: [69 MB] #3 In the peak calling step, the following will be performed simultaneously:
INFO @ 11 Aug 2023 11:54:16: [69 MB] #3 Write bedGraph files for treatment pileup (after scaling if necessary)... H3K4me3_WT_treat_pileup.bdg
INFO @ 11 Aug 2023 11:54:16: [69 MB] #3 Write bedGraph files for control lambda (after scaling if necessary)... H3K4me3_WT_control_lambda.bdg
INFO @ 11 Aug 2023 11:54:16: [69 MB] #3 Call peaks for each chromosome...
INFO @ 11 Aug 2023 11:54:16: [70 MB] #4 Write output xls file... ./MACS/H3K4me3_KO_vs_WT/H3K4me3_WT_peaks.xls
INFO @ 11 Aug 2023 11:54:16: [70 MB] #4 Write broad peak in broadPeak format file... ./MACS/H3K4me3_KO_vs_WT/H3K4me3_WT_peaks.broadPeak
INFO @ 11 Aug 2023 11:54:16: [70 MB] #4 Write broad peak in bed12/gappedPeak format file... ./MACS/H3K4me3_KO_vs_WT/H3K4me3_WT_peaks.gappedPeak
INFO @ 11 Aug 2023 11:54:16: [70 MB] Done!