Sponsored Content
Full Discussion: cdrom will not eject
Operating Systems Solaris cdrom will not eject Post 40834 by davidg on Wednesday 24th of September 2003 05:09:40 AM
Old 09-24-2003
Hi denisca,

Unix never lies. It realy means the device is busy. It can have several causes. Your current working directory resides on the mounted CD. Or maybe your previous ksh still resides in there. fuser -cu /SD_CDROM should tell you more. This shows you the current runnning prcesses on this FS. ps -ef and than look for possible processes running on this FS might clear out some as well.
It is very important to first make sure all processes have stopped on this FS before stoppping and restarting mountd.

Good luck

Regs David
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Eject Tape

Hi, I'm using AIX and I'm looking for a command that can eject the tape. Any help is highly appreciated. Regards, BS (3 Replies)
Discussion started by: bbhavis
3 Replies

2. Shell Programming and Scripting

eject floppy messages

Anyone know if there is a way to keep the "/dev/floppy/... can now be ejected" messages from coming up on the screen? I'm using Solaris 8 and it pops a message up, which is fine, but it also writes text in the terminal session... that is what I'm trying to avoid. I have tried running in silent... (4 Replies)
Discussion started by: Serious_Lee
4 Replies

3. Solaris

Tape eject using nsrjb

We have just got a Sun L8 tape library and I was trying to script a couple of things. One was to eject (export) a tape from the machine. nsrjb seems to have an enormous amount of options but this is one thing I have not been able to do. Anybody ever managed to do it? Cheers (1 Reply)
Discussion started by: Argus
1 Replies

4. AIX

Eject CDROM?

Now i have a prolem! I double click on my zip file from cdrom. System can not read my zip file and i can not eject my cdrom. How can i manage process and can i end a process or how can i eject my cdrom? please have me! thanks (4 Replies)
Discussion started by: leenguyen0101
4 Replies

5. Solaris

SF V210 CDROM drive auto eject!

Hi, When I insert a cd to CDROM drive in SF V210 Solaris 10 it took seconds then eject it auto! How can I solve this issue? Thanks Regards :) (8 Replies)
Discussion started by: HishamN
8 Replies

6. AIX

eject dvd/cd

does someone knows how to eject a dvd/cd device? thx (2 Replies)
Discussion started by: jcpetela
2 Replies

7. Filesystems, Disks and Memory

eject virtual tape

Hi i´m working with aix 6.1 and DL4100 (virtual tape library from EMC) and i makes backups (mksysb) into virtual drive (virtual standalone drive). I need eject de tape when backup is finished and I don't now what command use. Thanks for your help. The commands mt and tctl doesn't works.... (0 Replies)
Discussion started by: wolaf
0 Replies

8. Solaris

CDROM will not eject - says device busy

Hi, I've seen similar posts on this board about ejecting CDROMs but I've tried the solutions people suggested but still cannot eject the CD. It's stuck in a production box so I can't reboot it... bash-3.00# eject -f cdrom /vol/dev/dsk/c0t0d0/sol_10_106_sparc/s0: Device busy bash-3.00#... (14 Replies)
Discussion started by: jimmy54321
14 Replies

9. Solaris

How to eject boot cdrom after booting from it?

Hey everyone, I currently have a sparcstation 5, and am trying to run some scripts on it without booting off the hard drive. Currently I am using a Solaris 8 install cd to boot into single user mode. However, the scripts I have are on a different CD. What I would like to do is to use the... (6 Replies)
Discussion started by: idlechatter
6 Replies

10. Solaris

Trying to eject cdrom

The green cdrom light is blinking on our Sun Solaris server. I tried the eject command to eject cdrom: eject cdrom cdrom: No such file or directory bash-2.05# eject No default media available bash-2.05# eject cdrom0 cdrom0: No such file or directory The message log file shows: Oct 19... (6 Replies)
Discussion started by: agarcia19
6 Replies
fuser(1M)						  System Administration Commands						 fuser(1M)

NAME
fuser - identify users of files and devices SYNOPSIS
/usr/sbin/fuser [-c | -d | -f] [-nu] [-k | -s sig] files [ [- ] [-c | -d | -f] [-nu] [-k | -s sig] files] ... DESCRIPTION
The fuser utility displays the process IDs of the processes that are using the files specified as arguments. Each process ID is followed by a letter code. These letter codes are interpreted as follows. If the process is using the file as c Indicates that the process is using the file as its current directory. m Indicates that the process is using a file mapped with mmap(2). See mmap(2) for details. n Indicates that the process is holding a non-blocking mandatory lock on the file. o Indicates that the process is using the file as an open file. r Indicates that the process is using the file as its root directory. t Indicates that the process is using the file as its text file. y Indicates that the process is using the file as its controlling terminal. For block special devices with mounted file systems, all processes using any file on that device are listed. For all types of files (text files, executables, directories, devices, and so forth), only the processes using that file are reported. For all types of devices, fuser also displays any known kernel consumers that have the device open. Kernel consumers are displayed in one of the following formats: [module_name] [module_name,dev_path=path] [module_name,dev=(major,minor)] [module_name,dev=(major,minor),dev_path=path] If more than one group of files are specified, the options may be respecified for each additional group of files. A lone dash cancels the options currently in force. The process IDs are printed as a single line on the standard output, separated by spaces and terminated with a single new line. All other output is written on standard error. Any user can run fuser, but only the superuser can terminate another user's process. OPTIONS
The following options are supported: -c Reports on files that are mount points for file systems, and any files within that mounted file system. -d Report device usage information for all minor nodes bound to the same device node as the specified minor node. This option does not report file usage for files within a mounted file system. -f Prints a report for the named file, not for files within a mounted file system. -k Sends the SIGKILL signal to each process. Since this option spawns kills for each process, the kill messages may not show up immediately (see kill(2)). No signals will be sent to kernel file consumers. -n Lists only processes with non-blocking mandatory locks on a file. -s sig Sends a signal to each process. The sig option argument specifies one of the symbolic names defined in the <signal.h> header, or a decimal integer signal number. If sig is a symbolic name, it is recognized in a case-independent fashion, without the SIG pre- fix. The -k option is equivalent to -s KILL or -s 9. No signals will be sent to kernel file consumers. -u Displays the user login name in parentheses following the process ID. EXAMPLES
Example 1 Reporting on the Mount Point and Files The following example reports on the mount point and files within the mounted file system. example% fuser -c /export/foo Example 2 Restricting Output when Reporting on the Mount Point and Files The following example reports on the mount point and files within the mounted file system, but the output is restricted to processes that hold non-blocking mandatory locks. example% fuser -cn /export/foo Example 3 Sending SIGTERM to Processes Holding a Non-blocking Mandatory Lock The following command sends SIGTERM to any processes that hold a non-blocking mandatory lock on file /export/foo/my_file. example% fuser -fn -s term /export/foo/my_file ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of fuser: LANG, LC_ALL LC_CTYPE, LC_MES- SAGES, and NLSPATH. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Standard | +-----------------------------+-----------------------------+ SEE ALSO
ps(1), mount(1M), kill(2), mmap(2), signal(3C), attributes(5), environ(5), standards(5) NOTES
Because fuser works with a snapshot of the system image, it may miss processes that begin using a file while fuser is running. Also, pro- cesses reported as using a file may have stopped using it while fuser was running. These factors should discourage the use of the -k option. SunOS 5.11 21 Oct 2003 fuser(1M)
All times are GMT -4. The time now is 06:27 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy