Thomas Schmitt wrote:
Hi,
Richard Owlett wrote:
I did a rerun. The only apparent change in test conditions was I used a
different instance of Mate Terminal.
...
4460664832 bytes (4.5 GB) copied, 798.488 s, 5.6 MB/s
...
richard@debian:~$ /sbin/isosize rerundvd9.iso
4460664832
Did the dd runs with short "ls -l" result tell the "isosize"
result, nevertheless ?
I think I did.
I'll revise my procedure to use the script command to keep better
records.
I've a gut feeling that Mate Terminal isn't redoing
blocks=$(expr $(/sbin/isosize /dev/sr0) / 2048)
every time.
Command interpretation is supposed to depend on the
shell interpreter (e.g. bash, dash, ksh) and not on the
terminal emulator (e.g. xterm, gnome-terminal, Konsole).
What should have been identical runs did not have identical
results -- part of reason I'll make extensive use of script
command in the next round.
On the first hand we have to concentrate on the messages
from the dd runs which deliver too few bytes in the .iso
files.
After a dd run turned out to copy not enough bytes, look
into the system log whether any error message about "sr0"
has been freshly recorded.
Steve McIntyre:
I'll tell you what's most likely wrong - you're storing your extracted
ISO images on a FAT32 filesystem which doesn't support file sizes
larger than 4GiB.
But why did the retry succeed ?
Richard: Did you copy to a different directory ?
When reusing a file name I had used filemanager to send file to
trash and then emptied trash before reusing.
Nagging memories of a similar problem with either Win95 or Win98.
We fiercely deny any similarity with said systems.
No bugs shared.
Why would creative minds need to "share" ;)
Have a nice day :)
Thomas
