FC2-test2-i386-DVD.iso was 4306010112 bytes, which is a multiple of 32KiB (specifically, 4306010112 bytes = 131409 32KiB-sized blocks).
However, FC2-test3-i386-DVD.iso is 4379752448 bytes, which is *not* a multiple of 32KiB:
$ factor 4379752448 4379752448: 2 2 2 2 2 2 2 2 2 2 2 2138551
Therefore, growisofs pads it by 18432 bytes up to 4379770880 bytes (133660 32KiB-sized blocks) when burning it. This makes it a pain to verify the MD5 checksums; instead of being able to just run md5sum on the device (e.g., "md5sum /dev/hdc"), you have to use dd to read only the size of the ISO (without the pad).
Was FC2-test3-i386-DVD.iso not being a multiple of 32KiB blocks in size intentional, or just an oversight? And will the DVD ISO for FC2 final be a multiple of 32KiB blocks in length?
On 30/04/04 08:09, James Ralston wrote:
FC2-test2-i386-DVD.iso was 4306010112 bytes, which is a multiple of 32KiB (specifically, 4306010112 bytes = 131409 32KiB-sized blocks).
However, FC2-test3-i386-DVD.iso is 4379752448 bytes, which is *not* a multiple of 32KiB:
$ factor 4379752448 4379752448: 2 2 2 2 2 2 2 2 2 2 2 2138551
Therefore, growisofs pads it by 18432 bytes up to 4379770880 bytes (133660 32KiB-sized blocks) when burning it. This makes it a pain to verify the MD5 checksums; instead of being able to just run md5sum on the device (e.g., "md5sum /dev/hdc"), you have to use dd to read only the size of the ISO (without the pad).
Was FC2-test3-i386-DVD.iso not being a multiple of 32KiB blocks in size intentional, or just an oversight? And will the DVD ISO for FC2 final be a multiple of 32KiB blocks in length?
Could this have contributed to my problem burning it?
I blanked the DVD+RW with
# growisofs -Z /dev/dvd=/dev/zero
(or something like that) just fine.
But when I'd burnt the DVD+RW with
# growisofs -dvd-compat -Z /dev/dvd=FC2-test3-i386-DVD.iso
it stayed at the stage of writing the lead-out for over an hour.
On 2004-04-30 at 08:34:33+01 Craig Emery fedora-test@cemery.org.uk wrote:
On 30/04/04 08:09, James Ralston wrote:
FC2-test3-i386-DVD.iso is 4379752448 bytes, which is *not* a multiple of 32KiB [...] Therefore, growisofs pads it by 18432 bytes up to 4379770880 bytes (133660 32KiB-sized blocks) when burning it. This makes it a pain to verify the MD5 checksums; instead of being able to just run md5sum on the device (e.g., "md5sum /dev/hdc"), you have to use dd to read only the size of the ISO (without the pad).
Could this have contributed to my problem burning it?
I doubt it, but if you want to test, just manually append 18432 bytes to FC2-test3-i386-DVD.iso, and try to burn it.
James