growisofs error - "unable to umount /dev/rdsk/c19t0d0"

[James IOCANE]

Hi,

I am trying to automate burning of an image to DVD for DR purposes. I am running into the following issue:

root@adlun001:/ #nice --9 growisofs -dvd-compat -Z /dev/rdsk/c19t0d0=/var/opt/ignite/dv>
root@adlun001:/ #nice --9 growisofs -dvd-compat -Z /dev/rdsk/c19t0d0=/var/opt/ignite/dvd_build_tmp/adlun001.iso
Executing 'builtin_dd if=/var/opt/ignite/dvd_build_tmp/adlun001.iso of=/dev/rscsi/c13t0l0 obs=32k seek=0'
:-( unable to umount /dev/rdsk/c19t0d0: No such file or directory
root@adlun001:/ #ls -l /dev/rdsk/c19t0d0
crw-r----- 1 bin sys 188 0x130000 May 19 12:16 /dev/rdsk/c19t0d0
root@adlun001:/ #

I beieve that this is the same issue as addressed in thread #1219445, however I don't understand the solution in this thread. I've scattered links around that should cover all the scenarios I can come up with in my head, but none help.

Does anyone understand what is going on with this?

ext_bus 19 255/1/0 usb_ms_scsi CLAIMED INTERFACE USB Mass Storage SCSI
target 14 255/1/0.0 tgt CLAIMED DEVICE
disk 6 255/1/0.0.0 sdisk CLAIMED DEVICE TEAC DV-W28ECWS
/dev/dsk/c19t0d0 /dev/rdsk/c19t0d0

[Dennis Handly]

>I believe that this is the same issue as addressed in thread #1219445

Please include a URL to make it easy:
http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1219445

Does this exist?
of=/dev/rscsi/c13t0l0

[James IOCANE]

Yes, it does exist.

crw------- 1 root sys 203 0x130002 May 26 11:24 c13t0l0

The growisofs program spits a different error if that special file is not there.

the "13" in c13t0l0 would appear to be part of what the previous thread was talking about when it spoke of some parts of growisof working in decimal, and some in hex.

I am considering changing the instance of the bus to something other than 19 to short circuit the problem.

[V. Nyga]

Hi,

I think it should be:
crw-r----- 1 root sys 203 0x130002 May 26 11:24 c13t0l0

not
crw------- 1 root sys 203 0x130002 May 26 11:24 c13t0l0

Is there a reason that /dev/rdsk/c19t0d0 has the same address like /dev/rscsi/c13t0l0?

Volkmar

[James IOCANE]

I'm trying to do the burn as root, so permissions of 0700 should be fine. Additionally, that's exactly what is created by the command line suggested by growisofs.

The reason that c13t0l0 is c13 not c19 as far as I can tell is that growisofs looks for the wrong special file. It's hearing /dev/rdsk/c19t0d0 for the rscsi device converting the 19 to hex (13) and looking for that file name for the rscsi device. Whatever; creating precisely that special file passes the test that growisofs uses. The test itself may be broken also; this is the problem I am trying to solve.

James

[James IOCANE]

Is there anyone who has any knowledge of this issue?