about cdrom

[leyearn]

my system is hp9000 D270
os version is 10.20
#mount -F cdfs -o ro /dev/dsk/c1t2d0 /cdrom
/dev/dsk/c1t2d0: Device busy
#fuser -cu /cdrom
/cdrom: fuser: could not find file system mounted at /cdrom.
#showmount -a
#
#ioscan -funC disk
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
disk 0 8/4.3.0 sdisk CLAIMED DEVICE SEAGATE ST34371W
/dev/dsk/c0t3d0 /dev/rdsk/c0t3d0
disk 1 8/4.4.0 sdisk CLAIMED DEVICE SEAGATE ST34371W
/dev/dsk/c0t4d0 /dev/rdsk/c0t4d0
disk 2 8/4.5.0 sdisk CLAIMED DEVICE DGC C2300WDR5
/dev/dsk/c0t5d0 /dev/rdsk/c0t5d0
disk 3 8/16/5.2.0 sdisk CLAIMED DEVICE TOSHIBA CD-ROM XM-5701T
A
/dev/dsk/c1t2d0 /dev/rdsk/c1t2d0
disk 4 8/16/5.6.0 sdisk CLAIMED DEVICE SEAGATE ST34371N
/dev/dsk/c1t6d0 /dev/rdsk/c1t6d0
#ly_noma2/> diskinfo -v /dev/rdsk/c1t2d0
SCSI describe of /dev/rdsk/c1t2d0:
vendor: TOSHIBA
product id: CD-ROM XM-5701TA
type: CD-ROM
size: 0 Kbytes
bytes per sector: 0
rev level: 1347
blocks per disk: 0
ISO version: 0
ECMA version: 0
ANSI version: 2
removable media: yes
response format: 2
(Additional inquiry bytes: (32)35 (33)2f (34)31 (35)34 (36)2f (37)39 (38)37 (
39)0 (40)0 (41)0 (42)0 (43)0 (44)0 (45)0 (46)0 (47)0 (48)0 (49)0 (50)0 (51)0 (52
)0 (53)0 (54)0 (55)0 (56)0 (57)0 (58)0 (59)0 (60)0 (61)0 (62)0 (63)0 (64)0 (65)0
(66)0 (67)0 (68)0 (69)0 (70)0 (71)0 (72)0 (73)0 (74)0 (75)0 (76)0 (77)0 (78)0 (
79)0 (80)0 (81)0 (82)0 (83)0 (84)0 (85)0 (86)0 (87)0 (88)0 (89)0 (90)0 )

what's wrong with my cdrom?

[Hoefnix]

Can it be that the CDROM is mounted to another mountpoint?
Just type : mount | grep c1t2d0

Regards,

Peter

[leyearn]

ly_noma2/> mount |grep c1t2d0
ly_noma2/>

[leyearn]

#mount |grep c1t2d0
#

[Elmar P. Kolkman]

fuser -c only works on the root directory of a file system. What you need to do is to check whether /cdrom is empty or not (ls -a /cdrom) and if it is do an fuser on the directory.

Other things to test:
fuser /dev/dsk/c1t2d0
fuser /dev/rdsk/c1t2d0
showmount -e (it might be exported but not yet mounted remotely. This will also result in this error.)

For testing purposes, create a new directory and try mounting your drive at that point.

[Elena Leontieva]

Check that no pfs daemons are using the device:
ps -ef | grep pfs

Elena