09-20-2011
Try to track down and kill any processes still using the share. That may allow it to finish unmounting.
If not, you may have to reboot. You'll never kill a lazy unmount. IMHO -l amounts to a denial-of-service bug: Open files will hold it open, but new ones can't be opened, causing a situation where there's no service and you can't force it to complete.
This User Gave Thanks to Corona688 For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
:confused: Twofold question for you unix "guru's"
1) When attempting to use the umount command I get a message stating that the partition that I want to unmount is busy. Is there another command that I need to use prior to the umount command to clear the partition of activity????? ... (2 Replies)
Discussion started by: rod23
2 Replies
2. UNIX for Dummies Questions & Answers
I'm trying to unmount a file system, but umount says the device is busy. A fuser -c /myfs tells me that nothing on this fs is in use. Any idea?
Oh, and btw, why isn't my signature beeing displayed? Show user's signature is enabled and I have entered one :/ (10 Replies)
Discussion started by: sTorm
10 Replies
3. 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
4. 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
5. 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
6. 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
7. HP-UX
sorry, wrong section, mod please close thread (0 Replies)
Discussion started by: robertngo
0 Replies
8. 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
9. 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
10. 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
LEARN ABOUT PHP
systemd-halt.service
SYSTEMD-HALT.SERVICE(8) systemd-halt.service SYSTEMD-HALT.SERVICE(8)
NAME
systemd-halt.service, systemd-poweroff.service, systemd-reboot.service, systemd-kexec.service, systemd-shutdown - System shutdown logic
SYNOPSIS
systemd-halt.service
systemd-poweroff.service
systemd-reboot.service
systemd-kexec.service
/lib/systemd/systemd-shutdown
/lib/systemd/system-shutdown/
DESCRIPTION
systemd-halt.service is a system service that is pulled in by halt.target and is responsible for the actual system halt. Similarly,
systemd-poweroff.service is pulled in by poweroff.target, systemd-reboot.service by reboot.target and systemd-kexec.service by kexec.target
to execute the respective actions.
When these services are run, they ensure that PID 1 is replaced by the /lib/systemd/systemd-shutdown tool which is then responsible for the
actual shutdown. Before shutting down, this binary will try to unmount all remaining file systems, disable all remaining swap devices,
detach all remaining storage devices and kill all remaining processes.
It is necessary to have this code in a separate binary because otherwise rebooting after an upgrade might be broken -- the running PID 1
could still depend on libraries which are not available any more, thus keeping the file system busy, which then cannot be re-mounted
read-only.
Immediately before executing the actual system halt/poweroff/reboot/kexec systemd-shutdown will run all executables in
/lib/systemd/system-shutdown/ and pass one arguments to them: either "halt", "poweroff", "reboot" or "kexec", depending on the chosen
action. All executables in this directory are executed in parallel, and execution of the action is not continued before all executables
finished.
Note that systemd-halt.service (and the related units) should never be executed directly. Instead, trigger system shutdown with a command
such as "systemctl halt" or suchlike.
SEE ALSO
systemd(1), systemctl(1), systemd.special(7), reboot(2), systemd-suspend.service(8)
systemd 237 SYSTEMD-HALT.SERVICE(8)