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 | | > |