On Wed, 14 Jul 1999, Douglas Gilbert wrote:
> I posed a question about this on the
> [EMAIL PROTECTED] newsgroup and found out
> some interesting information.
>
> It seems that iso9660 CDs often have 2 or more
> "run out" blocks which may or may not be visible
> when a READ CAPACITY is done. There is a utility
> that comes with xcdroast called 'isosize' which
> I think delves into the iso9660 table of contents
> to work out the length. This is probably a more
> accurate figure than the READ CAPACITY that sg_dd2048
> and dd most likely use.
Yes, I know this.
The output of 'isosize' is wrong too. It's the same as sg_readcap gives
you.
But the read with sg_dd2048 minus 2 blocks was perfect. The read with dd
and the same block-count was wrong. dd fails to 7 sectors (not 2). Even if
I reduce the block count by 2, it fails.
> Further, both sg_dd2048 and dd (I guess) read multiple
> blocks at a time to improve performance. So if there
> is an IO error on one of the latter blocks in a
> multi-block sequence, then you won't see any of the
> blocks from that sequence in your output file.
The muliple block read of sg_dd2048 works perfect. The problem is, that I
get into trouble, if I use dd on /dev/scd0. The scsi-cdrom driver seems to
be buggy, because it handles the reading of the last blocks wrong.
Gruss
Sven
--
>>> "I am the embodiment of modern medicine." <<<<<<< Der Dativ ist dem <<<<<<<
>>>>>> The holographic doctor, USS-Voyager <<<<<<<<<< Genitiv sein Tod. <<<<<<<
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>> http://www.fmi.uni-passau.de/~anderss >< email: [EMAIL PROTECTED] <<
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
