Filesize on NAS not 'shrinked'

[hpk60]

I do a shrink-backup from a 32GB microSDXC to a mounted directory on my NAS.
shrink-backup shows the following summary:

Number of files: 112,213 (reg: 95,477, dir: 8,599, link: 8,135, dev: 2)
Number of created files: 0
Number of deleted files: 486 (reg: 2, dir: 107, link: 376, dev: 1)
Number of regular files transferred: 5
Total file size: 3.39G bytes
Total transferred file size: 196.91K bytes
Literal data: 196.96K bytes
Matched data: 0 bytes
File list size: 2.82M
File list generation time: 2.904 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 3.07M
Total bytes received: 62.00K

sent 3.07M bytes received 62.00K bytes 189.62K bytes/sec
total size is 3.39G speedup is 1,083.56

Backup location: /NAS/backup/wovo.img
Write to logfile: false
Autoexpand filesystem at boot: true
Use exclude.txt: false
Boot partition: true
Bootsector size: 519MiB
Estimated root usage: 28351MiB
Image size: 29646MiB with a root partition of 29126MiB
Please wait for the system to reboot after restoring an image with autoexpansion

However, Windows Explorer shows me a wovo.img with 30'357'720KB
When I look at the file details I get the following information:

Filesize: 28.9 GB
Size on disk: 3.93 GB

Why is the filesize not shrinked as well? Do I need to activate any options?
I just used shrink-backup -a

Thanks for your feedback

[hpk60]

My error, the microSDXC seems to be that full - sorry ...

Problem solved:
sudo fsck -y /dev/sda2
fsck from util-linux 2.41
e2fsck 1.47.2 (1-Jan-2025)
rootfs: recovering journal
Setting free inodes count to 1726701 (was 1726706)
Setting free blocks count to 267240 (was 267239)
rootfs: clean, 111603/1838304 files, 7391384/7658624 blocks

[UnconnectedBedna]

Glad you got it working!
You might also want to take into consideration that windows might show you megabytes (power of 1000) instead of what shrink-backup is using, ie mebibytes (power of 1024). 1mebibyte = 1.048576megabytes

But I am confused, the img was supposed to be 29646MiB (28.95GiB) but it was 3.93G?
And shrink-backup did not indicate that the created img file failed during truncation (resizing) due to the device being full?

I would have loved to take a look at that logfile, but I see you ran it without log so nvm. :)

I'll close this issue since you indicate it is working after making sure you had sufficient space on the device you saved the img.

[UnconnectedBedna]

Lol, wait, this is not an issue, it's a discussion!
Let's open it again.. xD

[hpk60]

It was definitely not an issue with shrink-backup. It was a problem with the filesystem.
After fsck could repair the file system, shrink-backup worked as expected and did a 6GB backup of the 32GB microSDXC card. 5-6GB was, what I expected and when I saw the 30GB file on windows, I assumed, shrink-backup did not shrink ... shame on me, should have checked more before posting here.

Anyway, thank you for the very useful tool. As mentioned, now it works as expected and I can update existing backups very fast. No more need for sloww dd's ...