Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
When trying to unmount (via umount) a file system, I get 2 infamous "device is busy" messages. I've used both the lsof and fuser commands but nothing gets returned that references the file system I'm trying to unmount.
I've even tried to force an unmount, but that didn't work either. What was even more weird was that (as a test) I created a file on that file system and had it open and then used the lsof / fuser command to see what response I would get. Basically the response from both commands was blank.
Short of removing the mount entry from /etc/fstab and rebooting, is there another method for determining what file/process is attached to the file system that would cause it to show up as device is busy? Is there another method for forcing an unmount?
If you were viewing the filesystem in a filemanager such as Konquerer, or if you had a console open into that filesystem (as in cd to the filesystem), then the filesystem is busy. You will have to cd out of the filesystem, or close the file manager to release the filesystem for umount.
What is the mount point for the device? You said you ran lsof. Hmm, that should show you if any programs are blocking it. Make sure you run lsof as root (or with sudo), and use fgrep, like this:
Thanks for the reply...however...I've tried the lsof | fgrep command and as far as I know there are no known consoles that are open to this filesystem. There must be a hung process or file somewhere that's attached to the filesystem. I've also used who extensively but that didn't reveal any login in sessions either.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.