Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then 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.
This is the problem I'm having: when I try to unmount any of my samba shares, the system tells me I can't because the "device is busy". I ran fuser on the directory, and it tells me that famd is accessing the smb share.
It's the file alteration monitor (little typo you had there, stuNNed), which is used so that your file manager will automatically refresh/update when you move, copy, delete files in a fm window without you having to manually hit the "refresh" button to see the update.
Seems that something is somehow misconfigured, though; I don't think that should be happening. But just killing it so you can unmount is a good temporary workaround until you get it fixed.
I ended up doing "dpkg-reconfigure fam", and after that, I was able to unmount my samba shares. In any case, I don't know what triggers this behavior, but doing the above mentioned fixes the problem once it happens
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.