mount: /dev/dsk/c1t2d0 on /SD_CDROM : Device busy

[Jerry_109]

Hello All,

Does anyone know why I cannot mount my cdrom ?

######################################
root@hohp226[/root]
# uname -a ; model
HP-UX hohp226 B.11.11 U 9000/800/rp7410


root@hohp226[/root]
# mount -F cdfs /dev/dsk/c1t2d0 /cdrom
mount: /dev/dsk/c1t2d0 on /cdrom : Device busy
root@hohp226[/root]
#
root@hohp226[/root]
# ls -ld /cdrom
drwx------ 2 root sys 96 May 8 13:25 /cdrom


root@hohp226[/root]
# /etc/ioscan -nfkC disk | more
Class I H/W Path Driver S/W State H/W Type Description
=========================================
disk 1 1/0/0/3/1.2.0 sdisk CLAIMED DEVICE HP DVD-ROM 305
/dev/dsk/c1t2d0 /dev/rdsk/c1t2d0



root@hohp226[/root]
# diskinfo /dev/rdsk/c1t2d0
SCSI describe of /dev/rdsk/c1t2d0:
vendor: HP
product id: DVD-ROM 305
type: CD-ROM
size: 645712 Kbytes
bytes per sector: 2048


root@hohp226[/root]
# fuser -u /cdrom
/cdrom:


root@hohp226[/root]
# ps -ef | grep mount
root 3888 1 0 Apr 16 ? 0:00 /usr/sbin/rpc.mountd
root 334 23618 0 13:41:31 pts/1 0:00 grep mount

[Steven E. Protter · Accepted solution]

Shalom,

fuser -cuk /SD_CDROM

That will kill any proceses mounting it.

Check to see if other mounts are on the cd/rom using other names such as /cdrom

SEP

[Jerry_109]

root@hohp226[/root]
# fuser -cuk /cdrom
/cdrom: fuser: could not find file system mounted at /cdrom.

[Bill Hassell]

The most common reason for device busy when mounting is that someone has cd'ed into the directory. Since the permission for /cdrom is 700, only root can be there so check all root shells -- or make sure there is only one root shell process (yours).

fuser is unfortunately very poor at identifying open files and directories. Also, I would never use the -k option until I checked every process listed by fuser (without -k). You can unexpectedly kill an application and possibly corrupt data. Download a copy of lsof so you can really see the open files and processes.

In the meantime, mount the CDROM at a different location:

mkdir /cdrom1
mount /dev/dsk/c1t2d0 /cdrom1

You normally do not need the -F cdfs for CDROMs.

[TTr]

One other possibility is that /dev/dsk/c1t2d0 is already mounted under a different mountpoint. Check it with the "bdf" command.

[Yogeeraj_1]

hi,

TTr:
> root@hohp226[/root]
> # mount -F cdfs /dev/dsk/c1t2d0 /cdrom
mount: /dev/dsk/c1t2d0 on /cdrom : Device busy
> root@hohp226[/root]


from above output, it seems that the cdrom has already been mounted and it is really on /cdrom


Questions:
- what command was used to mount the CDROM previously?

- Any errors reported for the device?


revert!
kind regards
yogeeraj

[TTr]

> root@hohp226[/root]
> # mount -F cdfs /dev/dsk/c1t2d0 /cdrom
> mount: /dev/dsk/c1t2d0 on /cdrom : Device busy
> root@hohp226[/root]

> from above output, it seems that the cdrom has already been mounted and it is really on /cdrom

On the contrary. If /dev/dsk/c1t2d0 was mounted under /cdrom the error would be "mount: /dev/dsk/c1t2d0 is already mounted on /cdrom".

The above error means that either /dev/dsk/c1t2d0 is busy (ie mounted somewhere else) or /cdrom is busy (a shell is cd-ed to it).

One other observation I have is that on the subject of this thread, the name /SD-CDROM is used. Everywhere else in the text, the name /cdrom is used.

I think we are not getting all the details here.

Also dare I say pfs may be involved?

[Jerry_109]

############################
Just a little history :

I can successfully mount to the cdrom drive when using another cd ( hp-ux Ent Oper Env )
and it works fine as displayed below:

The cd I'm having problems mounting was supplied by software developer ( Peoplesoft 8.49 )
they downloaded from PS registered website


root@hohp226[/root]
# mount -F cdfs /dev/dsk/c1t2d0 /cdrom
root@hohp226[/root]
# bdf /cdrom
Filesystem kbytes used avail %used Mounted on
/dev/dsk/c1t2d0 1971936 1971936 0 100% /cdrom
root@hohp226[/root]
###########################






root@hohp226[/root]
# bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/root 204800 200560 4240 98% /
/dev/vg00/stand 393392 69056 284992 20% /stand
/dev/vg00/var 4194304 1367280 2805696 33% /var
/dev/vg00/save 1048576 844017 191818 81% /var/adm/sw/save
/dev/vg00/crash 4194304 1471419 2552706 37% /var/adm/crash
/dev/vg00/usr 4194304 1310304 2861512 31% /usr
/dev/vg01/u99 114524160 101303400 13016628 89% /u99
/dev/vg01/u98 40632320 38223920 2258352 94% /u98
/dev/vg01/u100 36896768 11889026 24226330 33% /u100
/dev/vg01/u04 23552000 15555118 7747042 67% /u04
/dev/vg01/u03 40960000 33101198 7621454 81% /u03
/dev/vg01/u02 130457600 69806496 60185152 54% /u02
/dev/vg01/u01 231874560 183044312 48453472 79% /u01
/dev/vg01/u00 39936000 16556840 22703042 42% /u00
/dev/vg00/tmp 2097152 377048 1707656 18% /tmp
/dev/vg00/opt 2097152 1855416 239888 89% /opt
/dev/vg00/home 2097152 1792664 302136 86% /home
/dev/vg01/dohc 491520 245828 230398 52% /dohc
ecfhod3:/u08/ecf 98304000 34788144 63334504 35% /u08/ecf
root@hohp226[/root]

##################################

root@hohp226[/root]
# strings /etc/mnttab
/dev/vg00/root / vxfs log 0 1 1208331150
/dev/vg00/stand /stand hfs defaults 0 0 1208331152
/dev/vg00/var /var vxfs delaylog 0 0 1208331164
/dev/vg00/save /var/adm/sw/save vxfs delaylog 0 0 1208331165
/dev/vg00/crash /var/adm/crash vxfs delaylog 0 0 1208331165
/dev/vg00/usr /usr vxfs delaylog 0 0 1208331165
/dev/vg01/u99 /u99 vxfs delaylog 0 0 1208331165
/dev/vg01/u98 /u98 vxfs delaylog 0 0 1208331165
/dev/vg01/u100 /u100 vxfs delaylog 0 0 1208331165
/dev/vg01/u04 /u04 vxfs delaylog 0 0 1208331165
/dev/vg01/u03 /u03 vxfs delaylog 0 0 1208331166
/dev/vg01/u02 /u02 vxfs delaylog 0 0 1208331166
/dev/vg01/u01 /u01 vxfs delaylog 0 0 1208331166
/dev/vg01/u00 /u00 vxfs delaylog 0 0 1208331166
/dev/vg00/tmp /tmp vxfs delaylog 0 0 1208331167
/dev/vg00/opt /opt vxfs delaylog 0 0 1208331167
/dev/vg00/home /home vxfs delaylog 0 0 1208331167
/dev/vg01/dohc /dohc vxfs delaylog 0 0 1208331167
ecfhod3:/u08/ecf /u08/ecf nfs rsize=32768,wsize=32768,NFSv3 0 0 1208331430
root@hohp226[/root]


##################################

root@hohp226[/root]
# ps -aef | grep root | grep sh
root 4 0 0 Apr 16 ? 0:58 unhashdaemon
root 1031 1 0 Apr 16 ? 0:08 /opt/ssh/sbin/sshd
root 3391 1 0 Apr 16 ? 0:00 /bin/sh /opt/MultiLink/bin/LiebertM EM /opt/MultiLink em.cfg
root 5429 1 0 Apr 16 ? 0:00 /sbin/sh /usr/dt/bin/dtrc
root 719 1031 0 08:10:55 ? 0:00 sshd: root@pts/0
root 876 872 0 08:11:33 pts/1 0:00 -sh
root 9426 7771 1 08:40:38 pts/2 0:00 grep sh
root 872 1031 0 08:11:32 ? 0:00 sshd: root@pts/1
root 7768 1031 0 08:35:36 ? 0:00 sshd: root@pts/2
root 7771 7768 0 08:35:37 pts/2 0:00 -sh
root 722 719 0 08:10:56 pts/0 0:00 -sh
root 2635 722 0 08:16:51 pts/0 0:01 /bin/sh /tmp/istemp2635130081651/setup.hp.embedded -is:orig /u1


#################################

root@hohp226[/root]
# mkdir /cdrom1
root@hohp226[/root]
# mount -F cdfs /dev/dsk/c1t2d0 /cdrom1
mount: /dev/dsk/c1t2d0 on /cdrom1 : Device busy
root@hohp226[/root


##################################

root@hohp226[/root]
# ps -ef | grep pfs
root 10178 7771 1 08:45:18 pts/2 0:00 grep pfs
root@hohp226[/root]

[TTr]

I put a windows only CD in my UNIX workstation and got the same error as you were getting

mount: /dev/dsk/c0t0d0 on /cdrom : Device busy.

So most likely you have a windows only or a defective CD.

Have you try this CD in a windows PC?

You can try this,

1. Unmount any CD mountpoints, /cdrom, /cdrom1 etc.

2. Ensure that the CD drive is not mounted by using "bdf". The CD device must NOT be in the BDF output.

3. Check "man mount_cdfs" and scroll down in the options section " -o specific_options" and see if the "rr" option is available. If it is available mount the CD with

mount -F cdfs -o rr,cdcase /dev/dsk/c0t0d0 /cdrom

If it does not mount, the CD was created for a windows system.

Try putting it on a windows PC and upload its contents to the UNIX server.

[Jerry_109]

Thanks ,

I jsut checked with the developer, and you are correct, they gave me a windows only CD.

I mounted on my pc, and it loaded to my "D:"
drive with no problem. I will fto the data over to my Unix server.......... :>)