Running a backup on Weaviate 1.25.5 (Helm chart, single instance, S3 backend) left the backup stuck in STARTED state for hours on a tiny dataset (~7k objects), with the status endpoint never advancing. The reporter noted this happened even on a fresh single-instance install with plenty of free space, ruling out the usual disk-full explanation. Strace showed the server churning on LSM compaction scratch files during the backup, suggesting a stuck compaction blocking the backup's progress tracking.