I can confirm the SD does NOT have 'firmware'$'\n' on it. I've looked for it on a Windows and Mac machine and nothing shows it to be there.
I've also used SD Cloner to copy everything to a usb drive. 'firmware'$'\n' doesn't show up on any of my computers. The only time I ever see it is when image-backup runs.
You're idea to look inside 'firmware'$'\n' was interesting, it showed the following:
/mnt/rootfs/boot/firmware^J/boot/firmware
/mnt/rootfs/ is the mount location of the .img file, image-backup made.
I logged image-backup and a plain rsync -aDH to files. On image-backup, when it's generating a file list to backup it does not show 'firmware'$'\n' or /boot/firmware/boot/firmware. Only during the rsync [generator] phase does it show.
The plain rsync log shows no 'firmware'$'\n' - /boot/firmware/boot/firmware instance.
I honestly don't think this directory exists on the drive. Attached is a zip with the two log files. IB-error_cleaned is image-backups. I removed all other directories that rsync worked on in between the send, receive and generate phases. Many pages worth. I've highlighted any reference to /boot/firmware in both log files.
I'm not an rsync export but I would think running rsync -aDH from the command line should produce the same "'firmware'$'\n' /boot/firmware/boot/firmware " if the file does indeed exist, right?
Edit: Out of curiousity, what version of rsync are you using?
I've also used SD Cloner to copy everything to a usb drive. 'firmware'$'\n' doesn't show up on any of my computers. The only time I ever see it is when image-backup runs.
You're idea to look inside 'firmware'$'\n' was interesting, it showed the following:
/mnt/rootfs/boot/firmware^J/boot/firmware
/mnt/rootfs/ is the mount location of the .img file, image-backup made.
I logged image-backup and a plain rsync -aDH to files. On image-backup, when it's generating a file list to backup it does not show 'firmware'$'\n' or /boot/firmware/boot/firmware. Only during the rsync [generator] phase does it show.
Code:
2024/03/13 15:57:11 [43302] [generator] pushing local filters for /tmp/img-backup-mnt/boot/2024/03/13 15:57:11 [43302] [generator] make_file(boot/firmware,*,2)2024/03/13 15:57:11 [43302] delete_item(boot/firmware) mode=40755 flags=22024/03/13 15:57:11 [43302] [generator] pushing local filters for /tmp/img-backup-mnt/boot/firmware/2024/03/13 15:57:11 [43302] [generator] make_file(boot/firmware/boot,*,2)2024/03/13 15:57:11 [43302] [generator] pushing local filters for /tmp/img-backup-mnt/boot/firmware/boot/2024/03/13 15:57:11 [43302] [generator] make_file(boot/firmware/boot/firmware,*,2)2024/03/13 15:57:11 [43302] [generator] pushing local filters for /tmp/img-backup-mnt/boot/firmware/boot/firmware/2024/03/13 15:57:11 [43302] [generator] popping local filters2024/03/13 15:57:11 [43302] delete_item(boot/firmware/boot/firmware) mode=40755 flags=42024/03/13 15:57:11 [43302] [generator] popping local filters2024/03/13 15:57:11 [43302] cannot delete non-empty directory: boot/firmware/boot2024/03/13 15:57:11 [43302] delete_item(boot/firmware/boot) mode=40755 flags=42024/03/13 15:57:11 [43302] cannot delete non-empty directory: boot/firmware/boot2024/03/13 15:57:11 [43302] [generator] popping local filters2024/03/13 15:57:11 [43302] cannot delete non-empty directory: boot/firmwareI honestly don't think this directory exists on the drive. Attached is a zip with the two log files. IB-error_cleaned is image-backups. I removed all other directories that rsync worked on in between the send, receive and generate phases. Many pages worth. I've highlighted any reference to /boot/firmware in both log files.
I'm not an rsync export but I would think running rsync -aDH from the command line should produce the same "'firmware'$'\n' /boot/firmware/boot/firmware " if the file does indeed exist, right?
Edit: Out of curiousity, what version of rsync are you using?
Code:
rsync version 3.2.7 protocol version 31Copyright (C) 1996-2022 by Andrew Tridgell, Wayne Davison, and others.Web site: https://rsync.samba.org/Capabilities: 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints, socketpairs, symlinks, symtimes, hardlinks, hardlink-specials, hardlink-symlinks, IPv6, atimes, batchfiles, inplace, append, ACLs, xattrs, optional secluded-args, iconv, prealloc, stop-at, no crtimesOptimizations: no SIMD-roll, no asm-roll, openssl-crypto, no asm-MD5Checksum list: xxh128 xxh3 xxh64 (xxhash) md5 md4 sha1 noneCompress list: zstd lz4 zlibx zlib noneDaemon auth list: sha512 sha256 sha1 md5 md4Statistics: Posted by mdpaxton — Thu Mar 14, 2024 12:36 am