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