Polytropon wrote:
I'd like to ask how to determine which process (or program) keeps a partition
in state "busy" so that umount will refuse to unmount this partition. I found
this when going into SUM for checking and maintenance, so I think it would be
good to check which program still accesses files on a specific partition
allthough it should already be terminated due to the different "stop" mechanisms
run for the services in /etc/rc.d and /usr/local/etc/rc.d respectively, which
is performed by init, if I understood this correctly.


        % shutdown now

        ... going SUM, starting sh ...

        # umount /home
        # umount /tmp
        # umount /var
        # umount /usr
        umount: unmount of /usr failed: Device busy
        # umount -f /usr
        # mount -o ro /
        # fsck ... blah blah ...

It would be good to be able to check why the partition is in state "busy" and
possible terminate / kill processes that cause this. Using the force (-f) seems
to be unneccessarily unfriendly. =^_^=

Thanks for suggestions!

Most commonly for me is because my $PWD (or CWD) is in the filesystem i intend to umount so as a habit now, i move myself to the root partition (when logged in as root) via the following, and assuming I want to umount /usr

# umount /usr
umount: unmount of /usr failed: Device busy
# cd
# umount /usr

cd, with no arguments, move you to ~ (aka $HOME)

freebsd-questions@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Reply via email to