Kill -9 not killing application, connected with cdrom busy error?
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Distribution: Slackware 14 (Server),OpenSuse 13.2 (Laptop & Desktop),, OpenSuse 13.2 on the wifes lappy
Posts: 781
Rep:
Kill -9 not killing application, connected with cdrom busy error?
Hi everyone,
This is similar to many other threads, but with no answwer that I have found yet. If there is one, then I apologise in advance for repeating the question.
My problem is, when I have mounted a cd under /mnt/scd1 as root, then I am unable to umount it. By issuing the command umount /mnt/scd1, I get the error message " umount failed device is busy"
If I go lsof /mnt/scd1 I get this:- mount 14621 root cwd DIR 11,1 6144 296960 /mnt/scd1
I then issue the command kill -9 14621, which I understand should kill that process, as the -9 is meant to be not ignored, but to no avail.
Can anyone help, I am becoming more follically challenged by the minute!.
If you are in the directory tree for the device it will not let you umount it. That may be what is going on. Look at all your terminals and make sure that you are not in a dirctory of the mounted device.
Distribution: Slackware 14 (Server),OpenSuse 13.2 (Laptop & Desktop),, OpenSuse 13.2 on the wifes lappy
Posts: 781
Original Poster
Rep:
Hello,
No, I am not in the directory tree for the cdrom. I had puposely made sure to cd away from it completely. However, hera is something else that I found out that looks like it is connected to whatever is casuing this. When I reboot, because I can find no other way to umount. Then I get a list of errors telling me that /usr /root / cannot be umounted because the device is busy. Also, this means on the reboot that fsck runs, but doesn't find any errors with the file system. Any more ideas?
Distribution: Slackware 14 (Server),OpenSuse 13.2 (Laptop & Desktop),, OpenSuse 13.2 on the wifes lappy
Posts: 781
Original Poster
Rep:
Thanks, I will try that next time it happens. Am currently using MDK9.2, and this has been a problem for some time which I have just lived with. It normally happens after issuing a urpmi command for update or install of software from a CD. I suppose I should have said that as a normal user, it never happens. At least I have learnt another linux (or is it a specific Mandrake one) with command with fuser.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.