Re: Packet writing not working for me either... Willing to help debug.
On Monday 15 July 2002 11:18 pm, you wrote:
Ok, quick question.. are you using a CDRW, or a DVD+RW in your DVD+RW drive?
If your using a DVD+RW, none of the packet stuff should be applicable. I think DVD+RW is closer to DVD-RAM and HD's in that you "format" the media. Once formated, you can freely write anywhere on the disc. (so all you'd have to do is run mkudffs on the disc - assuming the kernel thinks the device is R/W)
Ben
I think you are confusing DVD RAM nd DVD RW. From my understanding, and from what I've read at http://fy.chalmers.se/~appro/linux/DVD+RW/ , DVD RAM is like a slow hard disk, Random access, while DVD+RW is packeted just like CD RW. Considering that the software over there works in linux, im guessing he's right :P -- Wayde Milas Rarcoa (630) 654-2580
On Tue, Jul 16, 2002 at 11:12:28AM -0500, Wayde Milas wrote:
On Monday 15 July 2002 11:18 pm, you wrote:
Ok, quick question.. are you using a CDRW, or a DVD+RW in your DVD+RW drive?
If your using a DVD+RW, none of the packet stuff should be applicable. I think DVD+RW is closer to DVD-RAM and HD's in that you "format" the media. Once formated, you can freely write anywhere on the disc. (so all you'd have to do is run mkudffs on the disc - assuming the kernel thinks the device is R/W)
Ben
I think you are confusing DVD RAM nd DVD RW. From my understanding, and from what I've read at http://fy.chalmers.se/~appro/linux/DVD+RW/ , DVD RAM is like a slow hard disk, Random access, while DVD+RW is packeted just like CD RW. Considering that the software over there works in linux, im guessing he's right :P
Well, from http://fy.chalmers.se/~appro/linux/DVD+RW/ Q. Kernel patch? What's wrong with cdrecord/cdrtools? A. Nothing! Moreover, you actually need them (cdrtools). It's just that you can't use them to manage DVD+RW media itself. DVD+RW media has no notion of [multiple] sessions or packet writing, so cdrecord[-ProDVD] wouldn't really know what to do. But most important is that DVD+RW is a true random write access media and therefore is suitable for housing of arbitrary filesystem, e.g. ext2, vfat, ufs, etc. =]
From my understanding, its more like CD-MRW in that it does the write coalessing for you (which is why the packet driver wouldn't be needed), but it doesn't do bad block remapping so running arbitrary filesystems isn't the best way to go if you value your data.
Ben
Well, from http://fy.chalmers.se/~appro/linux/DVD+RW/
Q. Kernel patch? What's wrong with cdrecord/cdrtools? A. Nothing! Moreover, you actually need them (cdrtools). It's just that you can't use them to manage DVD+RW media itself. DVD+RW media has no notion of [multiple] sessions or packet writing, so cdrecord[-ProDVD] wouldn't really know what to do. But most important is that DVD+RW is a true random write access media and therefore is suitable for housing of arbitrary filesystem, e.g. ext2, vfat, ufs, etc.
=]
From my understanding, its more like CD-MRW in that it does the write coalessing for you (which is why the packet driver wouldn't be needed), but it doesn't do bad block remapping so running arbitrary filesystems isn't the best way to go if you value your data.
Ben
Bah. You got me. I didnt see that part (not quite sure how I missed it). Oh well, looks like im stuck with isofs :P -- Wayde Milas Rarcoa (630) 654-2580
On Tue, Jul 16, 2002 at 12:07:18PM -0500, Wayde Milas wrote:
Bah. You got me. I didnt see that part (not quite sure how I missed it). Oh well, looks like im stuck with isofs :P
So formating it, then running mkudffs /dev/scd0 (or whatever) fails? Ben
On Tuesday 16 July 2002 04:25 pm, Ben Fennema wrote:
On Tue, Jul 16, 2002 at 12:07:18PM -0500, Wayde Milas wrote:
Bah. You got me. I didnt see that part (not quite sure how I missed it). Oh well, looks like im stuck with isofs :P
So formating it, then running mkudffs /dev/scd0 (or whatever) fails?
Ben
Well, kinda. format it then: alumbox mkudffs # ./mkudffs /dev/sr0 trying to change type of multiple extents and thats it. No errors, no nothing. nothing in dmesg either. :( if i then try to mount it it fails (obviously) alumbox mkudffs # mount -t udf /dev/sr0 /mnt/cdrom mount: block device /dev/sr0 is write-protected, mounting read-only mount: wrong fs type, bad option, bad superblock on /dev/sr0, or too many mounted file systems Wayde
On Tue, Jul 16, 2002 at 09:25:23PM -0500, Wayde Milas wrote:
On Tuesday 16 July 2002 04:25 pm, Ben Fennema wrote:
On Tue, Jul 16, 2002 at 12:07:18PM -0500, Wayde Milas wrote:
Bah. You got me. I didnt see that part (not quite sure how I missed it). Oh well, looks like im stuck with isofs :P
So formating it, then running mkudffs /dev/scd0 (or whatever) fails?
Ben
Well, kinda. format it then:
alumbox mkudffs # ./mkudffs /dev/sr0 trying to change type of multiple extents
and thats it. No errors, no nothing. nothing in dmesg either. :(
It's not detecting the # of blocks. Try specifying it explicitly. i.e., mkudffs /dev/sr0 4589843 Ben
It's not detecting the # of blocks. Try specifying it explicitly.
i.e., mkudffs /dev/sr0 4589843
Ben
Ok, now it gets a bit more interesting. it looks like it formats with: alumbox mkudffs # ./mkudffs /dev/sr0 4589843 start=0, blocks=16, type=RESERVED start=16, blocks=3, type=VRS start=19, blocks=237, type=USPACE start=256, blocks=1, type=ANCHOR start=257, blocks=16, type=PVDS start=273, blocks=1, type=LVID start=274, blocks=4589312, type=PSPACE start=4589586, blocks=1, type=ANCHOR start=4589587, blocks=239, type=USPACE start=4589826, blocks=16, type=RVDS start=4589842, blocks=1, type=ANCHOR But when I try and mount it, I get: alumbox mkudffs # mount -t udf /dev/sr0 /mnt/cdrom mount: block device /dev/sr0 is write-protected, mounting read-only mount: wrong fs type, bad option, bad superblock on /dev/sr0, or too many mounted file systems And some debug messages in dmesg: UDF-fs DEBUG lowlevel.c:57:udf_get_last_session: XA disk: no, vol_desc_start=0 UDF-fs DEBUG super.c:1421:udf_read_super: Multi-session=0 UDF-fs DEBUG super.c:410:udf_vrs: Starting at sector 16 (2048 byte sectors) UDF-fs DEBUG super.c:1157:udf_check_valid: Failed to read byte 32768. Assuming open disc. Skipping validity check UDF-fs DEBUG misc.c:285:udf_read_tagged: location mismatch block 256, tag 0 != 256 UDF-fs DEBUG super.c:1211:udf_load_partition: No Anchor block found UDF-fs: No partition found (1) Also, when i do the ./mkudffs /dev/sr0 4589843 I see no disc activity whatsoever on the drive, yet there are no error messages in dmesg. Im guessing that mkudffs isnt actually writting anything to the drive? Wayde
On Wed, Jul 17, 2002 at 08:06:29AM -0500, Wayde Milas wrote:
Ok, now it gets a bit more interesting. it looks like it formats with:
alumbox mkudffs # ./mkudffs /dev/sr0 4589843 start=0, blocks=16, type=RESERVED start=16, blocks=3, type=VRS start=19, blocks=237, type=USPACE start=256, blocks=1, type=ANCHOR start=257, blocks=16, type=PVDS start=273, blocks=1, type=LVID start=274, blocks=4589312, type=PSPACE start=4589586, blocks=1, type=ANCHOR start=4589587, blocks=239, type=USPACE start=4589826, blocks=16, type=RVDS start=4589842, blocks=1, type=ANCHOR
But when I try and mount it, I get:
alumbox mkudffs # mount -t udf /dev/sr0 /mnt/cdrom mount: block device /dev/sr0 is write-protected, mounting read-only mount: wrong fs type, bad option, bad superblock on /dev/sr0, or too many mounted file systems
And some debug messages in dmesg:
UDF-fs DEBUG lowlevel.c:57:udf_get_last_session: XA disk: no, vol_desc_start=0 UDF-fs DEBUG super.c:1421:udf_read_super: Multi-session=0 UDF-fs DEBUG super.c:410:udf_vrs: Starting at sector 16 (2048 byte sectors) UDF-fs DEBUG super.c:1157:udf_check_valid: Failed to read byte 32768. Assuming open disc. Skipping validity check UDF-fs DEBUG misc.c:285:udf_read_tagged: location mismatch block 256, tag 0 != 256 UDF-fs DEBUG super.c:1211:udf_load_partition: No Anchor block found UDF-fs: No partition found (1)
Also, when i do the ./mkudffs /dev/sr0 4589843 I see no disc activity whatsoever on the drive, yet there are no error messages in dmesg. Im guessing that mkudffs isnt actually writting anything to the drive?
Apply the kernel patch (http://fy.chalmers.se/~appro/linux/DVD+RW/linux-2.4.patch) and try again.. you should have better luck (with the mkudffs) Ben
On Wednesday 17 July 2002 12:38 pm, Ben Fennema wrote:
Apply the kernel patch (http://fy.chalmers.se/~appro/linux/DVD+RW/linux-2.4.patch) and try again.. you should have better luck (with the mkudffs)
Ben
Patch applied semi-cleanly with jsut some offsets agains 19-rc2. mkudfs no appears to create the file system.. disk spins, no errors. the disc now mounts no problem : /dev/sr0 on /mnt/cdrom type udf (rw) However i cant write anything to the disc. I get : alumbox thebard # cp -a blah /mnt/cdrom cp: cannot create directory `/mnt/cdrom/blah': Input/output error and in dmesg: UDF-fs INFO UDF 0.9.6-rw (2002/03/11) Mounting volume 'LinuxUDF', timestamp 2002/07/17 14:28 (1ed4) I/O error: dev 0b:00, sector 1096 So, I reformat the dvd and try again. this time im able to copy a small .c file over no problem. But then I try and copy over a larger directory and cp segfaults :P. dmesg is nasty with: UDF-fs INFO UDF 0.9.6-rw (2002/03/11) Mounting volume 'LinuxUDF', timestamp 2002/07/17 14:47 (1ed4) I/O error: dev 0b:00, sector 1680 UDF-fs DEBUG inode.c:1835:udf_next_aext: reading block 420 failed! I/O error: dev 0b:00, sector 1680 Unable to handle kernel NULL pointer dereference at virtual address 00000034 printing eip: c0196e70 *pde = 00000000 Oops: 0000 CPU: 0 EIP: 0010:[<c0196e70>] Not tainted EFLAGS: 00010246 eax: 00000092 ebx: 00000000 ecx: f7383f3c edx: f74c7e40 esi: 0000005e edi: f74c7e40 ebp: 00000036 esp: f7383b08 ds: 0018 es: 0018 ss: 0018 Process cp (pid: 4630, stackpage=f7383000) Stack: f7723600 000001a4 00000000 00000000 f7383b7c f7383b74 f7383b70 f7383b6c f7383b70 f7383b6c 0000002b 00000000 00000000 00000000 00000000 07000000 00000028 00000036 00000000 00000000 f73bc964 f7723600 00000092 0000005e Call Trace: [<c01f5bde>] [<c01f59b0>] [<c01faf94>] [<c01e0d78>] [<c01e0e57>] [<c01eef0c>] [<c013c6d0>] [<c013c96c>] [<c019f161>] [<c01950b4>] [<c019e8e8>] [<c013b932>] [<c013c6d0>] [<c013c96c>] [<c019f161>] [<c01966e6>] [<c018da24>] [<c018eea8>] [<c019073e>] [<c0197bd7>] [<c014e1c0>] [<c01463bb>] [<c01464b8>] [<c010902b>] Code: 8b 7b 34 8b 49 08 01 f9 89 4c 24 50 c7 44 24 04 00 00 00 00 I/O error: dev 0b:00, sector 1680 UDF-fs DEBUG inode.c:1325:udf_update_inode: bread failure I/O error: dev 0b:00, sector 1672 UDF-fs DEBUG misc.c:274:udf_read_tagged: block=418, location=144: read failed udf: udf_read_inode(ino 418) failed !bh Thats from the mount, to the small 1 file copy, to teh large dir copy, to the ls. I'm thinking the patch just isnt ready for prime time? I've emailed the patch author, but hes on vacation for 2 weeks. Maybe he can shed some light on the situation. Another thing that comes to mind is that its possible dvd +rw media can only write in a sequential order.. ie, can it backup and rewrite over a block without blanking the media first? -- Wayde Milas Rarcoa (630) 654-2580
On Wed, Jul 17, 2002 at 03:13:46PM -0500, Wayde Milas wrote:
On Wednesday 17 July 2002 12:38 pm, Ben Fennema wrote:
Apply the kernel patch (http://fy.chalmers.se/~appro/linux/DVD+RW/linux-2.4.patch) and try again.. you should have better luck (with the mkudffs)
Ben
Patch applied semi-cleanly with jsut some offsets agains 19-rc2.
mkudfs no appears to create the file system.. disk spins, no errors.
the disc now mounts no problem : /dev/sr0 on /mnt/cdrom type udf (rw)
However i cant write anything to the disc. I get : alumbox thebard # cp -a blah /mnt/cdrom cp: cannot create directory `/mnt/cdrom/blah': Input/output error
and in dmesg: UDF-fs INFO UDF 0.9.6-rw (2002/03/11) Mounting volume 'LinuxUDF', timestamp 2002/07/17 14:28 (1ed4) I/O error: dev 0b:00, sector 1096
Just a though, but try: dd if=/dev/zero of=/dev/sr0 bs=2048 count=5120 mkudffs /dev/sr0 5120 mount try and copy stuff and see if you have any better luck. Ben
On Wednesday 17 July 2002 04:09 pm, Ben Fennema wrote:
Just a though, but try:
dd if=/dev/zero of=/dev/sr0 bs=2048 count=5120 mkudffs /dev/sr0 5120
mount try and copy stuff
and see if you have any better luck.
Nopers. The create worked, but the same problem when I tried to copy the mkudffs dir over: cp -a mkudffs /mnt/cdrom cp: cannot create directory `/mnt/cdrom/mkudffs': Input/output error dmesg: UDF-fs INFO UDF 0.9.6-rw (2002/03/11) Mounting volume 'LinuxUDF', timestamp 2002/07/17 19:27 (1ed4) I/O error: dev 0b:00, sector 1096 :( Wayde
participants (2)
-
Ben Fennema -
Wayde Milas