Advanced users • Re: Image File Utilities - Rsync file has vanished warnings

I am having some rsync "file has vanished" warnings when backing up my Raspberry Pi 4 LEMP server using your "image-backup" script.
Here is whats happening:

Code:

sudo /usr/local/bin/image-backup -u --initial /mnt/Backups/$(date +\%Y\-\%m\-\%d\_\%H\.\%M\.\%S)-IMAGE_UTILS-MANUAL_BACKUP-UBUNTU_22.04_Server.imgStarting full backup (for incremental backups, run: /usr/local/bin/image-backup  /mnt/Backups/2025-03-10_07.45.46-IMAGE_UTILS-MANUAL_BACKUP-UBUNTU_22.04_Server.img)file has vanished: "/var/log/journal/b798672adf844d119305ce190713facd/system@53316684db9b4767ab590cad0b60c178-0000000006729252-00062ff71f437735.journal"rsync warning: some files vanished before they could be transferred (code 24) at main.c(1338) [sender=3.2.7]e2fsck 1.46.5 (30-Dec-2021)Pass 1: Checking inodes, blocks, and sizesPass 2: Checking directory structurePass 3: Checking directory connectivityPass 4: Checking reference countsPass 5: Checking group summary informationwritable: 901623/4554752 files (0.3% non-contiguous), 15641309/18208000 blocksresize2fs 1.46.5 (30-Dec-2021)Resizing the filesystem on /dev/loop9p2 to 15800593 (4k) blocks.The filesystem on /dev/loop9p2 is now 15800593 (4k) blocks long.resize2fs 1.46.5 (30-Dec-2021)Resizing the filesystem on /dev/loop9p2 to 15795840 (4k) blocks.The filesystem on /dev/loop9p2 is now 15795840 (4k) blocks long.resize2fs 1.46.5 (30-Dec-2021)Resizing the filesystem on /dev/loop9p2 to 15795831 (4k) blocks.The filesystem on /dev/loop9p2 is now 15795831 (4k) blocks long.e2fsck 1.46.5 (30-Dec-2021)Pass 1: Checking inodes, blocks, and sizesPass 2: Checking directory structurePass 3: Checking directory connectivityPass 4: Checking reference countsPass 5: Checking group summary informationwritable: 901623/3956736 files (0.3% non-contiguous), 15603849/15795831 blocks

Is this error common when running Image-backup on a Live Ubuntu server? What is the meaning of these warnings, and are they anything I should be worried about? i.e. Can this cause corruption in the bootable image, or affect the final .img file negatively in any way? Should I be worried about this? Why are the journal files vanishing, and, how can I make these journal files NOT VANISH while backing up? Thoughts please?

rsync first builds a list of files to copy. If a file is moved, deleted, renamed, etc. before rsync gets around to copying it, rsync displays a warning. This should not be anything to worry about. If it really bothers you, you can perform an incremental update to pick up the change.

Statistics: Posted by Danrancan — Tue May 13, 2025 6:58 pm