has anyone else the problem with "Free block count wrong" or "Free inodes count wrong" while doing a MANUALLY fsck on a recovered Linux VM? (Ubuntu, Debian doesnt matter - ext4)
These "issues" are not in the Live-Systems
I can correct these manually or a new boot run with fsck will correct it - but is it normal? Backup Mode is "vmware tools quiescence" with CBT and SAN-Mode on ESXi 5.5 (newest Veeam-Release)