Changes between Initial Version and Version 1 of Ticket #8460, comment 14


Ignore:
Timestamp:
Apr 11, 2012, 5:58:02 PM (12 years ago)
Author:
scdbackup

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #8460, comment 14

    initial v1  
    11Replying to [comment:13 jahaiku]:
    2 > Replying to [comment:10 scdbackup]:
    3 > > I am the developer of xorriso.
    4 > >
    5 > > You may let it report block addresses of data files, which should
    6 > > match the LBN from line 848 of iso9660.cpp:
    7 > > {{{
    8 > >          TRACE(("InitNode - data start LBN is %d\n",
    9 > >                 (int)node->startLBN[FS_DATA_FORMAT]));
    10 > > }}}
    11 > >
    12 > > The xorriso command would be
    13 > > {{{
    14 > >   xorriso -indev ...ISO-image-path... \
    15 > >           -find / -sort_lba -exec report_lba -- \
    16 > >   | less
    17 > > }}}
    18 > >
    19 > > It will print lines like
    20 > > {{{
    21 > > Report layout: xt , Startlba ,   Blocks , Filesize , ISO image path
    22 > > ...
    23 > > File data lba:  0 ,     1907 ,       11 ,    21781 , '/md5sum.txt'
    24 > > File data lba:  0 ,     1918 ,       71 ,   144786 , '/README.mirrors.html'
    25 > > File data lba:  0 ,     1989 ,       39 ,    78036 , '/README.mirrors.txt'
    26 > > ...
    27 > > }}}
    28 > > The column "Startlba" should match the "LBN" values from the trace.
    29 > >
    30 > > On a first glimpse, iso9660.cpp looks as if it was restricted to data
    31 > > files with a single data extent. This would restrict the size of a
    32 > > data file to 4 GiB-1. But this does not restrict the overall size of the
    33 > > image.
    34 > [[BR]]
    35 >
    362> I have checked this and the LBN-Value from the TRACE and the value (LBA) I got from xorriso is the same.
    37 > [[BR]]
     3> [[BR]
    384[[BR]]
    395
     
    4410and to what byte addresses they get converted.
    4511
     12I see another usage of startLBN which could lead to data file content. It is in function
     13{{{ fs_read_pages() }}} in iso9660/kernel_interface.cpp :
     14{{{
     15fileVec.offset = pos + node->startLBN[FS_DATA_FORMAT]
     16                * volume->logicalBlkSize[FS_DATA_FORMAT];
     17}}}
     18Again, {{{pos}}} , {{{node->startLBN[FS_DATA_FORMAT]}}}, and the resulting {{{fileVec.offset}}}
     19would be of interest.
     20
    4621Do all files show wrong content or does this happen only with those which have
    4722block numbers above 2097151 (= 4 GiB - 2 KiB) ?