08-07-2001
Check processes
To the umount:
Check any running processes on that mounted file system (including sub directories). A great tool for checking this is lsof (list open files). To kill user processes you can user the utility fuser (-ku) (but be careful with this). You might have to run fuser several times to get rid of all (stuck) processes.
To the fsck:
Depens on your OS and disk software. fsck is the standard and best tool for Linux.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
the program as follow:
mount /dev/fd0135ds18 /mnt
cd /mnt
touch file1
cat /file2 >/mnt/file1
umount /dev/fd135ds18
when error
tell device busy
could you tell me the reason? (1 Reply)
Discussion started by: fresh
1 Replies
2. UNIX for Advanced & Expert Users
hi all,
I inherit a Solaris7 system with /home mounted via a share from the NFS server. When I look at mnttab, there are two entries mounted under /home. Let's say they are server:/home/a and server:/home/b. I would like to maintain /home/a but not /home/b. However, I just don't know where... (4 Replies)
Discussion started by: andrec
4 Replies
3. Solaris
I am trying to umount a NFS share.
When I do the following:
# umount syrupg21
umount: /oebs/syrupg21: device is busy
device bussy so I like to check what is working on the system....
# fuser -muv /oebs/syrupg21/
#
So no locks should be there... any clue?
Regards,
Johan... (3 Replies)
Discussion started by: suntac
3 Replies
4. UNIX for Dummies Questions & Answers
Hi,
I am writing a multi-cd spanning installer for a particular software in Linux (Redhat 4 or greater / Suse )
My Program is in Java. A Shell Script is used to fork the java process. I found out that when the Installer tries to go to the next disc when prompted so, by the installer, the eject... (1 Reply)
Discussion started by: jiju.jacob
1 Replies
5. HP-UX
sorry, wrong section, mod please close thread (0 Replies)
Discussion started by: robertngo
0 Replies
6. HP-UX
Hello,
yeah... here my question :
Exist some way to force umount on HP other than reboot?
Thanks
gb (12 Replies)
Discussion started by: gogol_bordello
12 Replies
7. Linux
I had a umount busy issue, that the usual fuser -mk did not solve, I did a umount -l and was able to unmount the device, I then got in trouble by the storage team staff:
Here was a snippet of their response:
Using "umount -l" is a potentially dangerous act.
The command combination for a lazy... (8 Replies)
Discussion started by: pastajet
8 Replies
8. UNIX for Dummies Questions & Answers
Hi all,
I accidentally unmounted filesystems using umount -a command.
How to recover from this. Please help. Thanks in advance!
when i try to use mount -a i got the following output.
# mount -a
mount: /dev/vg00/lvol05 already mounted or /opt busy
mount: /dev/vg00/lvol07 already... (4 Replies)
Discussion started by: lramsb4u
4 Replies
9. UNIX for Dummies Questions & Answers
hi guys
I have to umount a CIFS from a Windows machine...but it's been imposible
there is one special task
/sbin/umount.cifs /mondobackup
that task cannot be kill...so I cannot umount the unit
any idea how to kill this and umount this CIFS share?
by the way I've tried
umount... (5 Replies)
Discussion started by: kopper
5 Replies
10. Linux
Hi,
initially i will mount a image using loop device using below command
mount -n -o loop,noatime,ro -t squashfs /mnt/fsh/bt.img /opt/app/test
then "mount" reflects with below
/dev/loop0 on /opt/app/test type squashfs (ro,noatime)
i will then umount using below commnd, umount is... (0 Replies)
Discussion started by: successlin
0 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