September 2002 - Packet Writing - openSUSE Mailing Lists

Problem with Tekram controller
by Kirill Messel 13 Sep '02

13 Sep '02

Hi all, I have Tekram 315 SCSI controller and SCSI CDRW Teac 512SB cdrwtool works fine. I can format the CD with udf file system. When i try to write small file to cd and after that "umount and mount" again i have got the following message: mount: wrong fs type, bad option, bad superblock on /dev/cdrecorder, or too many mounted file systems Why i can not to see my CD? Thanks Kirill

1 0

packetwriting on a parallel cdwriter?
by Guy Forssman 13 Sep '02

13 Sep '02

Hi, Is it possible to do packetwriting on a parallel CD-Writer such as the HP 7510e? Kernel is 2.4.19 I compiled the pktcdvd.o module and the UDF file format but I get a error when I do this: pktsetup /dev/pktcdvd0 /dev/pcd0 gives me this: drive not ready :Function not implemented Thanks in advance Guy Forssman

4 5

Re: Problems with packet-cd
by Frédéric L. W. Meunier 13 Sep '02

13 Sep '02

On 12 Sep 2002, Leo Przybylski wrote: > If you wish to do a format on Linux, you might try: > cdrwtool -d /dev/sr1 -m 4096 using device /dev/sr1 formatting 4096 blocks 8065KB internal buffer setting write speed to 12x But after I tried: # pktsetup /dev/pktcdvd /dev/sr1 # mkudffs --udfrev=0x0150 --media=cdrw /dev/sr1 trying to change type of multiple extents Am I missing something ? Do I need cdrwtool -d /dev/sr1 -b fast ? This is a new disk. I'm using the new UDF driver from CVS, with the namei.c changes. Tomorrow I'll format 2 disks with InCD 3.37, put files in one, let the other empty, and test both with packet-cd. > this will format the cd with cdrwtool in 4096 blocks. You > would probably use more blocks, but 4096 is a good test to > see if you get a seek error. > > On Thu, 2002-09-12 at 12:54, Frédéric L. W. Meunier wrote: > > On 12 Sep 2002, Leo Przybylski wrote: > > > > > /dev/pktcdvd0 and /dev/pktcdvd are for the pktcdvd module to > > > write to a a cdrw after mounting. > > > > I see, but I thought devfs would create /dev/pktcdvd0 and not > > /dev/pktcdvd. Are they different ? > > > > > If you use mount -t udf /dev/sr1 /mnt/cdrom, you will receive > > > a message telling you it is mounting read only. > > > > Yes, but after using packet-cd with the InCD 3.31 disk I now > > get a lot of messages in the logs (see my last mail) by only > > mounting it and reading the "corrupted" directories. > > > > If I could format it on Linux... > > > > Yesterday Ben fixed a bug in UDF CVS (present in 2.4.19) which > > prevented reading the contents after mounting. > > > > > On Thu, 2002-09-12 at 11:29, Frédéric L. W. Meunier wrote: > > > > I only noticed the new messages now. I think they only > > > > appeared after. > > > > > > > > >From my shell prompt, I see the commands completed at: > > > > > > > > pktsetup /dev/pktcdvd /dev/sr1 14:11:55 > > > > mount -t udf /dev/pktcdvd /mnt/cdrom 14:14:08 > > > > umount /mnt/cdrom 14:28:05 > > > > pktsetup -d /dev/pktcdvd 14:32:27 > > > > mount -t udf /dev/sr0 /mnt/cdrom 14:33:10 > > > > umount /mnt/cdrom 14:42:58 > > > > > > > > BTW, what's /dev/pktcdvc0 ? With devfs I only get /dev/pktcdvd. > > > > > > > > I'm using media ACER 8x. > > > > > > > > Sep 11 20:41:42 pervalidus kernel: hdd: ATAPI 40X CD-ROM CD-R/RW drive, 8192kB Cache, DMA > > > > hdd: HL-DT-ST GCE-8320B, ATAPI CD/DVD-ROM drive -- 0(a)pervalidus.{net, {dyndns.}org}

3 8

Re: Problems with packet-cd
by Frédéric L. W. Meunier 12 Sep '02

12 Sep '02

I only noticed the new messages now. I think they only appeared after. From my shell prompt, I see the commands completed at: pktsetup /dev/pktcdvd /dev/sr1 14:11:55 mount -t udf /dev/pktcdvd /mnt/cdrom 14:14:08 umount /mnt/cdrom 14:28:05 pktsetup -d /dev/pktcdvd 14:32:27 mount -t udf /dev/sr0 /mnt/cdrom 14:33:10 umount /mnt/cdrom 14:42:58 BTW, what's /dev/pktcdvc0 ? With devfs I only get /dev/pktcdvd. I'm using media ACER 8x. Sep 11 20:41:42 pervalidus kernel: hdd: ATAPI 40X CD-ROM CD-R/RW drive, 8192kB Cache, DMA hdd: HL-DT-ST GCE-8320B, ATAPI CD/DVD-ROM drive Sep 12 14:14:04 pervalidus kernel: pktcdvd: inserted media is CD-RW Sep 12 14:14:04 pervalidus kernel: pktcdvd: Fixed packets, 32 blocks, Mode-2 disc Sep 12 14:14:04 pervalidus kernel: pktcdvd: speed (R/W) 6/4 Sep 12 14:14:04 pervalidus kernel: pktcdvd: 590464kB available on disc Sep 12 14:14:04 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/lowlevel.c:57:udf_get_last_session: XA disk: no, vol_desc_start=0 Sep 12 14:14:04 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/super.c:1414:udf_read_super: Multi-session=0 Sep 12 14:14:04 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/super.c:407:udf_vrs: Starting at sector 16 (2048 byte sectors) Sep 12 14:14:08 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/super.c:750:udf_load_pvoldesc: recording time 1027278892/0, 2002/07/21 16:14 (1f4c) Sep 12 14:14:08 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/super.c:760:udf_load_pvoldesc: volIdent[] = 'Windows' Sep 12 14:14:08 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/super.c:767:udf_load_pvoldesc: volSetIdent[] = '3D3B325C' Sep 12 14:14:08 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/super.c:959:udf_load_logicalvol: Partition (0:0) type 2 on volume 1 Sep 12 14:14:08 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/super.c:969:udf_load_logicalvol: FileSet found in LogicalVolDesc at block=0, partition=0 Sep 12 14:14:08 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/super.c:797:udf_load_partdesc: Searching map: (0 == 0) Sep 12 14:14:08 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/super.c:838:udf_load_partdesc: unallocSpaceBitmap (part 0) @ 2 Sep 12 14:14:08 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/super.c:879:udf_load_partdesc: Partition (0:0 type 1522) starts at physical 1824, block length 293120 Sep 12 14:14:08 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/super.c:1212:udf_load_partition: Using anchor in block 256 Sep 12 14:14:08 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/super.c:1441:udf_read_super: Lastblock=0 Sep 12 14:14:08 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/super.c:722:udf_find_fileset: Fileset at block=0, partition=0 Sep 12 14:14:08 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/super.c:783:udf_load_fileset: Rootdir at block=20, partition=0 Sep 12 14:14:08 pervalidus kernel: UDF-fs INFO UDF 0.9.6 (2002/03/14) Mounting volume 'Windows', timestamp 2002/07/21 16:14 (1f4c) Sep 12 14:20:39 pervalidus kernel: udf: unknown compression code (117) stri=üè[^^ÿÿ\201ÃËí^A Sep 12 14:20:39 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/unicode.c:368:udf_get_filename: Failed in udf_get_filename: sname = uüè[^^ÿÿ\201ÃËí^A Sep 12 14:20:39 pervalidus kernel: udf: unknown compression code (117) stri=üè[^^ÿÿ\201ÃËí^A Sep 12 14:20:39 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/unicode.c:368:udf_get_filename: Failed in udf_get_filename: sname = uüè[^^ÿÿ\201ÃËí^A Sep 12 14:20:39 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/partition.c:40:udf_get_pblock: block=144, partition=257, offset=0: invalid partition Sep 12 14:20:39 pervalidus kernel: udf: unknown compression code (48) stri= Sep 12 14:20:39 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/unicode.c:368:udf_get_filename: Failed in udf_get_filename: sname = 0 Sep 12 14:20:49 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/partition.c:40:udf_get_pblock: block=144, partition=257, offset=0: invalid partition Sep 12 14:20:49 pervalidus kernel: udf: unknown compression code (48) stri= Sep 12 14:20:49 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/unicode.c:368:udf_get_filename: Failed in udf_get_filename: sname = 0 Sep 12 14:20:49 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/partition.c:40:udf_get_pblock: block=144, partition=257, offset=0: invalid partition Sep 12 14:20:49 pervalidus kernel: udf: unknown compression code (48) stri= Sep 12 14:20:49 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/unicode.c:368:udf_get_filename: Failed in udf_get_filename: sname = 0 Sep 12 14:21:02 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/partition.c:40:udf_get_pblock: block=144, partition=257, offset=0: invalid partition Sep 12 14:21:02 pervalidus kernel: udf: unknown compression code (48) stri= Sep 12 14:21:02 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/unicode.c:368:udf_get_filename: Failed in udf_get_filename: sname = 0 Sep 12 14:21:08 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/partition.c:40:udf_get_pblock: block=144, partition=257, offset=0: invalid partition Sep 12 14:21:08 pervalidus kernel: udf: unknown compression code (48) stri= Sep 12 14:21:08 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/unicode.c:368:udf_get_filename: Failed in udf_get_filename: sname = 0 Sep 12 14:21:17 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/partition.c:40:udf_get_pblock: block=144, partition=257, offset=0: invalid partition Sep 12 14:21:17 pervalidus kernel: udf: unknown compression code (48) stri= Sep 12 14:21:17 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/unicode.c:368:udf_get_filename: Failed in udf_get_filename: sname = 0 Sep 12 14:21:21 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/partition.c:40:udf_get_pblock: block=144, partition=257, offset=0: invalid partition Sep 12 14:21:21 pervalidus kernel: udf: unknown compression code (48) stri= Sep 12 14:21:21 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/unicode.c:368:udf_get_filename: Failed in udf_get_filename: sname = 0 Sep 12 14:21:21 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/partition.c:40:udf_get_pblock: block=144, partition=257, offset=0: invalid partition Sep 12 14:21:21 pervalidus kernel: udf: unknown compression code (48) stri= Sep 12 14:21:21 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/unicode.c:368:udf_get_filename: Failed in udf_get_filename: sname = 0 Sep 12 14:21:21 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/partition.c:40:udf_get_pblock: block=144, partition=257, offset=0: invalid partition Sep 12 14:21:21 pervalidus kernel: udf: unknown compression code (48) stri= Sep 12 14:21:21 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/unicode.c:368:udf_get_filename: Failed in udf_get_filename: sname = 0 Sep 12 14:25:53 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/partition.c:40:udf_get_pblock: block=2048, partition=175, offset=0: invalid partition Sep 12 14:26:28 pervalidus last message repeated 2 times Sep 12 14:26:44 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/partition.c:40:udf_get_pblock: block=2048, partition=175, offset=0: invalid partition Sep 12 14:32:27 pervalidus kernel: pktcdvd: writer sr1 unregistered Sep 12 14:33:10 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/lowlevel.c:57:udf_get_last_session: XA disk: no, vol_desc_start=0 Sep 12 14:33:10 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/super.c:1414:udf_read_super: Multi-session=0 Sep 12 14:33:10 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/super.c:407:udf_vrs: Starting at sector 16 (2048 byte sectors) Sep 12 14:33:10 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/super.c:750:udf_load_pvoldesc: recording time 1027278892/0, 2002/07/21 16:14 (1f4c) Sep 12 14:33:10 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/super.c:760:udf_load_pvoldesc: volIdent[] = 'Windows' Sep 12 14:33:10 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/super.c:767:udf_load_pvoldesc: volSetIdent[] = '3D3B325C' Sep 12 14:33:10 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/super.c:959:udf_load_logicalvol: Partition (0:0) type 2 on volume 1 Sep 12 14:33:10 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/super.c:969:udf_load_logicalvol: FileSet found in LogicalVolDesc at block=0, partition=0 Sep 12 14:33:10 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/super.c:797:udf_load_partdesc: Searching map: (0 == 0) Sep 12 14:33:10 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/super.c:838:udf_load_partdesc: unallocSpaceBitmap (part 0) @ 2 Sep 12 14:33:10 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/super.c:879:udf_load_partdesc: Partition (0:0 type 1522) starts at physical 1824, block length 293120 Sep 12 14:33:10 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/super.c:1212:udf_load_partition: Using anchor in block 256 Sep 12 14:33:10 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/super.c:1441:udf_read_super: Lastblock=0 Sep 12 14:33:10 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/super.c:722:udf_find_fileset: Fileset at block=0, partition=0 Sep 12 14:33:10 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/super.c:783:udf_load_fileset: Rootdir at block=20, partition=0 Sep 12 14:33:10 pervalidus kernel: UDF-fs INFO UDF 0.9.6 (2002/03/14) Mounting volume 'Windows', timestamp 2002/07/21 16:14 (1f4c) Sep 12 14:33:52 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/partition.c:40:udf_get_pblock: block=2048, partition=175, offset=0: invalid partition Sep 12 14:33:55 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/partition.c:40:udf_get_pblock: block=2048, partition=175, offset=0: invalid partition Sep 12 14:34:04 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/partition.c:40:udf_get_pblock: block=144, partition=257, offset=0: invalid partition Sep 12 14:34:04 pervalidus kernel: udf: unknown compression code (0) stri= Sep 12 14:34:04 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/unicode.c:368:udf_get_filename: Failed in udf_get_filename: sname = Sep 12 14:37:49 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/partition.c:40:udf_get_pblock: block=2048, partition=175, offset=0: invalid partition Sep 12 14:42:40 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/partition.c:40:udf_get_pblock: block=2048, partition=175, offset=0: invalid partition Sep 12 14:42:42 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/partition.c:40:udf_get_pblock: block=144, partition=257, offset=0: invalid partition Sep 12 14:42:42 pervalidus kernel: udf: unknown compression code (0) stri= Sep 12 14:42:42 pervalidus kernel: UDF-fs DEBUG ../linux-2.4/unicode.c:368:udf_get_filename: Failed in udf_get_filename: sname = -- 0(a)pervalidus.{net, {dyndns.}org}

3 4

cdrwtool formatting problems with scd0
by Leo Przybylski 12 Sep '02

12 Sep '02

Hello, I have been posting previously on a cdrw device and I have since solved my problems with that device. I've been trying since then with a different cdrw, so these questions are not related to the ones I've posted before. When I try to format a cdrw with the command: cdrwtool -d /dev/scd0 -m 1000 I get the following output: using device /dev/scd0 formatting 3000 blocks 1206KB internal buffer setting write speed to 12x wait_cmd: Invalid argument Command failed: 04 17 00 00 00 00 00 00 00 00 00 00 - sense 05.26.00 format disc: Illegal seek I continue to get this error until I raise the offset to >= 4000. Once I've done this it sits trying to format it for an hour or two until I eventually get the same error again. Any ideas? -Leo

1 0

Problems with packet-cd
by Frédéric L. W. Meunier 12 Sep '02

12 Sep '02

I tried with packet-cd 2.4.19-2 and UDF from CVS. cdrwtool -d /dev/sr1 -q using device /dev/sr1 8065KB internal buffer setting write speed to 12x Settings for /dev/sr1: Fixed packets, size 32 Mode-2 disc I'm going to do a quick setup of /dev/sr1. The disc is going to be blanked and formatted with one big track. All data on the device will be lost!! Press CTRL-C to cancel now. ENTER to continue. Initiating quick disc blank wait_cmd: Input/output error Command failed: a1 01 00 00 00 00 00 00 00 00 00 00 - sense 03.51.00 blank disc: Illegal seek And in the logs: Sep 12 14:00:14 pervalidus kernel: cdrom: This disc doesn't have any tracks I recognize! Sep 12 14:01:05 pervalidus kernel: sr1: CDROM (ioctl) error, command: 0xa1 01 00 00 00 00 00 00 00 00 00 00 Sep 12 14:01:05 pervalidus kernel: Current sr00:00: sns = 70 3 Sep 12 14:01:05 pervalidus kernel: ASC=51 ASCQ= 0 Sep 12 14:01:05 pervalidus kernel: Raw sense data:0x70 0x00 0x03 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x51 0x00 0x00 0x00 0x00 0x00 I also tried with a disk formatted with InCD 3.31 on Windows XP Professional. I used Midnight Commander to copy / remove files and directories: 1- I removed some files and added updated ones. They have the same name. It doesn't work. 2- Some files I added don't show up but when I try to copy them again mc reports they're the same. -- 0(a)pervalidus.{net, {dyndns.}org}

1 0

DVD+RW format blank option
by guStaVo ZaeRa 12 Sep '02

12 Sep '02

Andy, I was wondering whether there is a quick fix to reset the dvd+rw formatted bit on the media, so that next time i insert it into the drive, it'll seem like a new, previously unwritten media. I've looked at your code, and it seems like doing something like this would work: if( formats[8] == 2 && bBlank ) { formats[8] = 1; /* or something like that */ /* write to DVD+RW */ } CheerS, gustavo

2 1

creating udf fs on cd
by Leo Przybylski 12 Sep '02

12 Sep '02

Hello, I have found that cdrwtool -d /dev/scd1 -q has caused problems for me, so to debug the issue I tried to first blank and format the disc using: cdrwtool -d /dev/scd1 -b full -m 4096 Then, I try to apply a udf fs with cdrwtool -d /dev/scd1 -u 4096 When I try writing the fs, I get the following output: using device /dev/scd1 mkudffs 4096 blocks 1282KB internal buffer setting write speed to 12x 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=31, type=USPACE start=288, blocks=32, type=PVDS start=320, blocks=32, type=LVID start=352, blocks=32, type=STABLE start=384, blocks=1024, type=SSPACE start=1408, blocks=2400, type=PSPACE start=3808, blocks=31, type=USPACE start=3839, blocks=1, type=ANCHOR start=3840, blocks=160, type=USPACE start=4000, blocks=32, type=STABLE start=4032, blocks=32, type=RVDS start=4064, blocks=31, type=USPACE start=4095, blocks=1, type=ANCHOR Writing UDF structures to disc wait_cmd: Invalid argument Command failed: 2a 00 00 00 01 00 00 00 20 00 00 00 - sense 05.21.02 wait_cmd: Invalid argument Command failed: 2a 00 00 00 01 20 00 00 20 00 00 00 - sense 05.21.02 wait_cmd: Invalid argument Command failed: 2a 00 00 00 01 40 00 00 20 00 00 00 - sense 05.21.02 wait_cmd: Invalid argument Command failed: 2a 00 00 00 01 60 00 00 20 00 00 00 - sense 05.21.02 wait_cmd: Invalid argument Command failed: 2a 00 00 00 05 80 00 00 20 00 00 00 - sense 05.21.02 wait_cmd: Invalid argument Command failed: 2a 00 00 00 05 a0 00 00 20 00 00 00 - sense 05.21.02 wait_cmd: Invalid argument Command failed: 2a 00 00 00 05 c0 00 00 20 00 00 00 - sense 05.21.02 wait_cmd: Invalid argument Command failed: 2a 00 00 00 05 e0 00 00 20 00 00 00 - sense 05.21.02 wait_cmd: Invalid argument Command failed: 2a 00 00 00 06 00 00 00 20 00 00 00 - sense 05.21.02 wait_cmd: Invalid argument Command failed: 2a 00 00 00 0e e0 00 00 20 00 00 00 - sense 05.21.02 wait_cmd: Invalid argument Command failed: 2a 00 00 00 0f a0 00 00 20 00 00 00 - sense 05.21.02 wait_cmd: Invalid argument Command failed: 2a 00 00 00 0f c0 00 00 20 00 00 00 - sense 05.21.02 wait_cmd: Invalid argument Command failed: 2a 00 00 00 0f e0 00 00 20 00 00 00 - sense 05.21.02 I also try mkudffs --media-type=cdrw /dev/scd1 4096 I do not get the same errors, but I still cannot mount /dev/pktcdvd0 after executing pktsetup /dev/pktcdvd0 /dev/scd1 I must be doing something wrong. Anyone know what it is? -Leo http://www.foopan.ath.cx

2 1

mkudffs issues II
by guStaVo ZaeRa 11 Sep '02

11 Sep '02

Hello again, following up from the mkudffs issues message i posted yesterday.. Looking at the mkudffs source, i found that the application (mkudffs) prints out an error message, and exits without further information when the blocks > start_ext->blocks.. do you have an explanation of what actually happens here, Ben? :) I'm getting this error each time i try to run the mkudffs app through a 'system' function call from a C++ program. Another thing, is that the code looks like this: if (start == start_ext->start) { if (blocks == start_ext->blocks) { ... } else /* blocks > start_ext->blocks */ { printf("trying to change type of multiple extents\n"); exit(1); start_ext->space_type = type; return start_ext; } ..... The statements after the exit(1) are never reached.... why are they there? Thanks, gustavo

2 3

mkudffs issues III
by guStaVo ZaeRa 11 Sep '02

11 Sep '02

There's another thing i'd like to ask/point out about mkudffs... when formatted in Linux with UDF revision 1.5, a windows machine with ..... is not able to read the disc. I used the udf-verifier to compare the disc formatted with the windoze machine vs the Linux machine, and got this: windoze machine : ====> Encountered EntityID summary : count EntityID 3 Domain Entity Identifier Identifier : "*OSTA UDF Compliant" UDF revision : 1.50 Domain flags : #00 2 UDF Entity Identifier Identifier : "*UDF LV Info" UDF revision : 1.50 OS Class : #05 Windows 9x OS Identifier : #00 Windows 9x - Generic 2 UDF Entity Identifier Identifier : "*UDF Sparable Partition" UDF revision : 1.50 OS Class : #05 Windows 9x OS Identifier : #00 Windows 9x - Generic 2 UDF Entity Identifier Identifier : "*UDF Sparing Table" UDF revision : 1.50 OS Class : #05 Windows 9x OS Identifier : #00 Windows 9x - Generic 12 Implementation Entity Identifier Identifier : "*Veritas CPG file syste" OS Class : #05 Windows 9x OS Identifier : #00 Windows 9x - Generic 2 Application Entity Identifier Identifier : "*Veritas CPG file syste" Implementation Use : #05 #00 #00 #00 #00 #00 #00 #00 2 Application Entity Identifier Identifier : "+NSR02" Implementation Use : #50 #01 #05 #00 #00 #00 #00 #00 These EntityIDs are also shown above when read for the first time ====> Final verify status report Final UDF Revision range: 1.50 only File System info last valid block : 197951 block size : 2048 packet length : 16 nmb of sessions : 1 verify session : 1 session starts : 0 medium WR type : rewritable medium SE type : nonsequential Error count: 7 total occurrences: 14 Warning count: 1 total occurrences: 2 on the mkudffs formatted disc, i got this : ====> Encountered EntityID summary : count EntityID 2 Domain Entity Identifier Identifier : "*OSTA UDF Compliant" UDF revision : 1.50 Domain flags : #00 1 UDF Entity Identifier Identifier : "*UDF LV Info" UDF revision : 1.50 OS Class : #04 UNIX OS Identifier : #05 UNIX - Linux 1 UDF Entity Identifier Identifier : "*UDF Sparable Partition" UDF revision : 2.01 (illegal) OS Class : #04 UNIX OS Identifier : #05 UNIX - Linux Error: 1 error in this EntityID, UDF 2.1.5, 6.3, ECMA 1/7.4. 1 UDF Entity Identifier Identifier : "*UDF Sparing Table" UDF revision : 1.50 OS Class : #04 UNIX OS Identifier : #05 UNIX - Linux 10 Implementation Entity Identifier Identifier : "*Linux UDFFS" OS Class : #04 UNIX OS Identifier : #05 UNIX - Linux 1 Application Entity Identifier Identifier : "*Linux mkudffs" Implementation Use : #04 #05 #00 #00 #00 #00 #00 #00 1 Application Entity Identifier Identifier : "+NSR02" 1 error found in EntityID summary These EntityIDs are also shown above when read for the first time ====> Final verify status report Final UDF Revision range: 1.50 only File System info last valid block : 197951 block size : 2048 packet length : 32 nmb of sessions : 1 verify session : 1 session starts : 0 medium WR type : rewritable medium SE type : nonsequential Error count: 15 total occurrences: 81 Warning count: 0 total occurrences: 0 Note the UDF Entity Identifier on the mkudffs formatted disc... this doesn't seem right...? i specified the UDF revision to be 1.5! Is there something i'm missing out on, or did i actually spot a bug? :) gustavo

2 2