Changing the iso size from file size to space used
Sparse size
Sparse size should be shown because
all (non-modified) ISOs are the same size (GC 1 459 978 240 B, Wii 4 699 979 776 B) but the content size vary
the ISO padding should be sparse rather than removed (called trim in Wii Scrubber) because the latter is a more advanced modification leading to boot failure on the native hardware for some ISOs in some USB loaders
there's a command line tool to efficiently
sparse multiple files wit scrub *
backup rsync -aSv --progress /cygdrive/l/rom/ /cygdrive/e/backup/rom, move mv, copy cp with retained sparse information
Discussion
@delroth
I'm not sure if st_blocks unit size == 512 is a valid assumption to make, especially with 4K sectors disks.
st_blocks is 512 B for AF too
Is there any reference to the fact that st_blocks always counts 512 bytes blocks?
Changing the iso size from file size to space used
Sparse size
Sparse size should be shown because
wit scrub *rsync -aSv --progress /cygdrive/l/rom/ /cygdrive/e/backup/rom, movemv, copycpwith retained sparse informationDiscussion
@delroth
st_blocks is 512 B for AF too
The quote "the number of blocks allocated to the file, 512-byte units"
[03:16] @Sonicadvance1 JPeterson, Pull request #18, no
What's the reason that you oppose the change?