07-26-2002
Rather than "fuser -c /mysys", Try the block special file without the -c. Something like:
fuser /dev/dsk/c0t3d0s6
Also try lsof if you have it. I have better luck with lsof than I do with fuser.
10 More Discussions You Might Find Interesting
1. Programming
Hello,
I'm trying to obtain process memory contents using ptrace( ) on FreeBSD 4.7. I know this is neither portable nor clean, yet I'd really like to get it to work... I read the manual help page and did a google search, but couldn't find anything helpful.
First, the code I'm using to read an... (5 Replies)
Discussion started by: Driver
5 Replies
2. HP-UX
Anyone have any idea why I cannot umount a directory even though fuser shows no process attached to it?
fuser -cu /data/oracle/GMPSHRDM/export
/data/oracle/GMPSHRDM/export:
umount /data/oracle/GMPSHRDM/export
umount: cannot unmount /data/oracle/GMPSHRDM/export : Device busy
umount:... (2 Replies)
Discussion started by: keelba
2 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I'm trying to do a sharity mount to mount a terastation network drive.
I'm getting a Device or resource busy message after my mount command. Please see output below...
# /usr/local/sharity3/bin/sharity mount smb://labbackup01/bakup_data /mnt/labbackup01
Device or resource busy.... (2 Replies)
Discussion started by: orahi001
2 Replies
4. UNIX and Linux Applications
Ciao a tutti!!!
il mio problema è questo: sto cercando di inviare dei comandi AT da PC a cellulare utilizzando il bluetooth e cygwin e vorrei visualizzare le risposte nella shell bash. Per farlo apro due terminali utilizzando le seguente istruzioni:
xterm &
Sul primo scrivo
cat /dev/ttyS2
... (1 Reply)
Discussion started by: blianna
1 Replies
5. Solaris
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
6. Shell Programming and Scripting
I wish to umount in a bash script a specific device (/dev/sdb for example) that has multiple mounted file systems. how will I go about doing this?
Also is there a way to get a list of removable devices currently connected and offer the user a selection of them? (The devices themself not their... (2 Replies)
Discussion started by: temp4746
2 Replies
7. Linux
A product I am working on manages storage. We are currently porting it from Solaris to Linux.
The product allows its user, among other things, to add and remove file server volumes, where these volumes are exported using the NFS or the CIFS protocol.
The problem is that when the user requests to... (5 Replies)
Discussion started by: dhzdh
5 Replies
8. SCO
Hi there
After making a backup copy of it sometimes happens that when I want to unmount an NFS indicates the error:umount: /path_mount busy: Device busy (Error 16)
if I run lsoff, I can not find the process that is blocking the application.
I'm using OpenServer 5.0.2c as one NFS server ... (14 Replies)
Discussion started by: flako
14 Replies
9. HP-UX
Hi,
Unable to make tape backup, please help.
/opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00
* Creating local directories for configuration files and archive.
======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery.
(Mon... (4 Replies)
Discussion started by: anuragr
4 Replies
10. UNIX for Beginners Questions & Answers
mount -f nfs 1234:/export/ert /der/fr/ert
mount : /der/fr/ert: device busy
normally I will then do an
fuser filesystem
and kill the pids, which I did.
now if I do an fuser /der/fr/ert
I get the mount point and no pid
> fuser /der/fr/ert
/der/fr/ert:
but it... (1 Reply)
Discussion started by: goya
1 Replies
LEARN ABOUT FREEBSD
fuser
FUSER(1) BSD General Commands Manual FUSER(1)
NAME
fuser -- list IDs of all processes that have one or more files open
SYNOPSIS
fuser [-cfkmu] [-M core] [-N system] [-s signal] file ...
DESCRIPTION
The fuser utility writes to stdout the PIDs of processes that have one or more named files open. For block and character special devices,
all processes using files on that device are listed. A file is considered open by a process if it was explicitly opened, is the working
directory, root directory, jail root directory, active executable text, kernel trace file or the controlling terminal of the process. If -m
option is specified, the fuser utility will also look through mmapped files.
The following options are available:
-c Treat files as mount point and report on any files open in the file system.
-f The report must be only for named files.
-k Send signal to reported processes (SIGKILL by default).
-m Search through mmapped files too.
-u Write the user name associated with each process to stderr.
-M Extract values associated with the name list from the specified core instead of the default /dev/kmem.
-N Extract the name list from the specified system instead of the default, which is the kernel image the system has booted from.
-s Use given signal name instead of default SIGKILL.
The following symbols, written to stderr will indicate how files is used:
r The file is the root directory of the process.
c The file is the current workdir directory of the process.
j The file is the jail-root of the process.
t The file is the kernel tracing file for the process.
x The file is executable text of the process.
y The process use this file as its controlling tty.
m The file is mmapped.
w The file is open for writing.
a The file is open as append only (O_APPEND was specified).
d The process bypasses fs cache while writing to this file (O_DIRECT was specified).
s Shared lock is hold.
e Exclusive lock is hold.
EXIT STATUS
The fuser utility returns 0 on successful completion and >0 otherwise.
EXAMPLES
The command: ``fuser -fu .'' writes to standard output the process IDs of processes that are using the current directory and writes to stderr
an indication of how those processes are using the directory and user names associated with the processes that are using this directory.
SEE ALSO
fstat(1), ps(1), systat(1), iostat(8), pstat(8), vmstat(8)
STANDARDS
The fuser utility is expected to conform to IEEE Std 1003.1-2004 (``POSIX.1'').
HISTORY
The fuser utility appeared in FreeBSD 9.0.
AUTHORS
The fuser utility and this manual page was written by Stanislav Sedov <stas@FreeBSD.org>.
BUGS
Since fuser takes a snapshot of the system, it is only correct for a very short period of time. When working via kvm(3) interface the report
will be limited to filesystems the fuser utility knows about (currently only cd9660, devfs, nfs, ntfs, nwfs, udf, ufs and zfs).
BSD
May 13, 2011 BSD