dvdrtools-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Dvdrtools-users] Re: Problem burning multi-file images w/ Cendyne DVR-


From: John R. Makosky
Subject: [Dvdrtools-users] Re: Problem burning multi-file images w/ Cendyne DVR-104 -- 4GB "limit" is 32-bit POSIX
Date: 31 Dec 2002 11:42:34 -0600

Bryan,

Thanks for your prompt reply.  My comments and questions follow...

On Mon, 2002-12-30 at 16:09, Bryan J. Smith wrote:
> Quoting "John R. Makosky" <address@hidden>:
> > In short, I wish to burn 4+ GB to a DVD-R, but have to contend with
> > the Linux 2GB file-size limit.
> >  ...
> > OS:                 RedHat 6.2 on a Dell 2450 (PIII/866, 512MB RAM)
> > Kernel:     2.2.23 w/ ReiserFS patch
> 
> I think you just found the problem right there.
> 
> The 2-4GB file size limits are 32-bit POSIX ones.  They do not exist on 64-bit
> POSIX platforms (like Alpha, MIPS64, SPARC64, IA64, x86-64, etc...).

I just tried a similar experiment to my first one, this time using
roughly 1.9GB of data.  If I create a single-file ISO image from this
data, I can burn it to DVD-R with no problems.

However, if I create an ISO image over multiple files from the same
amount of data (using 'mkisofs -split-output'), I see the same problem
as before, namely, that attempts to write the second track fail. 
Typescript output of the session follows.  I find it difficult to
understand how the POSIX 32-bit limit would come into play in this
scenario.  I am also not a kernel hack.

Now... it may be that there is some incompatibility in the 2.2.x kernels
that is preventing me from burning DVD's from multiple-file images, and
I fully understand if Bernhard et. al. don't want to spend their time
working around ancient 2.2.x kernel bugs/limitations.  In that case,
I'll recommend that we follow Serge's suggestion, and port our
application to run on a distribution using the 2.4 kernel, and stop
wasting our time.

Is there anyone using multi-file images with ReiserFS in order to burn
4.5GB DVD's?  Is this a viable approach, or is it generally best to use
XFS or (horrors) JFS?

Thanks in advance,
john


Typescript output from 1.9GB multi-file image experiment:
--------------------------------------------------------

Script started on Tue Dec 31 16:13:55 2002
address@hidden iso]# /usr/local/bin/mkisofs -l -r -pad -split-output -o
test.iso foo
  0.54% done, estimate finish Tue Dec 31 16:17:10 2002

<snip>

 99.69% done, estimate finish Tue Dec 31 16:19:53 2002
Total translation table size: 0
Total rockridge attributes bytes: 1200067
Total directory bytes: 2207744
Path table size(bytes): 2208
Max brk space used 639bc4
932944 extents written (1822 Mb)
address@hidden iso]# ls -l
total 1867732
drwxr-xr-x   16 root     root         4096 Dec 31 16:13 foo
-rw-r--r--    1 root     root     1073741824 Dec 31 16:18 test.iso_00
-rw-r--r--    1 root     root     836927488 Dec 31 16:19 test.iso_01
address@hidden iso]# /usr/local/bin/dvdrecord -v -v -dummy dev=2,0,0
-dao speed=1 -data -nopad *.iso*
dvdrtools - based on:
Cdrecord 1.11a15 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jörg
Schilling
TOC Type: 1 = CD-ROM
/usr/local/bin/dvdrecord: Fifo not supported.
scsidev: '2,0,0'
scsibus: 2 target: 0 lun: 0
Linux sg driver version: 2.1.41
Using libscg version 'schily-0.5'
Using libscg transport code version 'schily-scsi-linux-sg.c-1.69'
atapi: 1
Device type    : Removable CD-ROM
Version        : 0
Response Format: 2
Capabilities   : 
Vendor_info    : 'PIONEER '
Identifikation : 'DVD-RW  DVR-104 '
Revision       : '1.20'
Device seems to be: Generic mmc2 DVD.
Using generic SCSI-3/mmc DVD-R(W) driver (mmc_mdvd).
Driver flags   : SWABAUDIO BURNFREE 
Supported modes: PACKET SAO
Drive buf size : 1638400 = 1600 KB
FIFO size      : 4194304 = 4096 KB
Track 01: data  1024 MB        
Track 02: data  798 MB        
track: 1 start: 0 pregap: 150
track: 2 start: 524438 pregap: 150
Total size:     2092 MB (207:21.25) = 933094 sectors
Lout start:     2093 MB (207:23/19) = 933094 sectors
 41 00 00 14 00 00 00 00
 41 01 00 10 00 00 00 00
 41 01 01 10 00 00 02 00
 41 02 00 10 00 74 20 26
 41 02 01 10 00 74 22 26
 41 AA 01 14 00 CF 17 13
Track 1 start 0
Track 2 start 524438
Track 3 start 933094
 41 00 A0 00 00 00 00 01 00 00 00 00
 41 00 A1 00 00 00 00 02 00 00 00 00
 41 00 A2 00 00 00 00 F7 23 19 00 00
 41 00 01 00 00 00 00 00 02 00 00 00
 41 00 02 00 00 00 00 16 34 38 00 00
Current Secsize: 2048
  ATIP start of lead in:  -150 (00:00/00)
Disk type:    unknown
Manuf. index: -1
Manufacturer: unknown (not in table)
Blocks total: 2298496 Blocks current: 2298496 Blocks remaining: 1365402
Starting to write CD/DVD at speed 1 in dummy mode for single session.
Last chance to quit, starting dummy write in 9 seconds.8
seconds.7 seconds.6 seconds.5
seconds.4 seconds.3 seconds.2
seconds.1 seconds.0 seconds. Operation starts.
trackno=0
BURN-Free is ON.
Sending CUE sheet...
/usr/local/bin/dvdrecord: WARNING: Drive returns wrong startsec (0)
using -150
Starting new track at sector: 0

Track 01:   0 of 1024 MB written.

<snip>

Track 01: Total bytes read/written: 1073741824/1073741824 (524288
sectors).
Starting new track at sector: 524438

Track 02:   0 of 798 MB written./usr/local/bin/dvdrecord: Input/output
error. write_g1: scsi sendcmd: no error
CDB:  2A 00 00 08 00 96 00 00 1F 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 05 00 00 00 00 0E 00 00 00 00 21 02 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x21 Qual 0x02 (logical block address out of range) [No
matching qualifier] Fru 0x0
Sense flags: Blk 0 (not valid) 
cmd finished after 0.006s timeout 200s

write track data: error after 0 bytes
Sense Bytes: 70 00 00 00 00 00 00 0E 00 00 00 00 00 00 00 00 00 00
Writing  time:  834.613s
Fixating...
WARNING: Some drives don't like fixation in dummy mode.
Fixating time:    2.991s

Script done on Tue Dec 31 16:35:42 2002









 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]