Backup App Inflating Target Size (17.6GB AppData Source Reaches 1.72TB+)

Hi everyone, I’d appreciate your help with this issue

Description When running a backup task for my AppData directory, the backup process enters what appears to be an infinite recursion loop. My original AppData source directory is 17.6 GB (34,533 files), but the target folder on the external drive has inflated to over 1.72 TB (74,450+ files) and keeps continuously increasing without finishing.

Steps to Reproduce

  1. Open the native ZimaOS Backup app.

  2. Configure a backup task:

    • From: /media/ZimaOS-HD/AppData

    • To: /media/Backup 500GB/AppData

  3. Start the backup process and monitor progress.

  4. Observe the destination file count and total size rapidly exceed the actual source size.

Expected vs Actual Behavior

  • Expected: The backup should mirror the ~17.6 GB source directory, respect symlinks/sockets, and complete successfully.

  • Actual: The backup engine continually duplicates files or traverses symlinks endlessly, reporting over 1.72 TB written to a 500GB target drive designation.

Before It Happened

  • Normal operation of Docker containers storing runtime data in /AppData.

Troubleshooting Tried

  • Monitored active container state during backup; plan to stop running Docker containers (docker stop $(docker ps -a -q)) to prevent runtime socket file or live cache changes during backups.

System Details

  • ZimaOS Version: ZimaOS 1.7.1 beta 2

  • Source Drive: /media/ZimaOS-HD/AppData

  • Backup Destination: /media/Backup 500GB/AppData

  1. journalctl -xe -u icewhale-files-backup > /DATA/icewhale-files-backup.log

  2. cp /var/log/icewhale/files-backup.log /DATA/files-backup.log

    Please run these two logs first, then send them to us. Thank you.