UbuntuThis forum is for the discussion of Ubuntu Linux.
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.
I have a network share mounted with cifs which does not work as expected. It should automount at boot and dismount at shutdown. It does not automount at boot, but "# mount -a" will mount it in the gui after booting finishes. This I can live with, but at shutdown or reboot, the cifs share hangs for about 30 seconds before dying. My /etc/fstab entry
I saw a bug report about the cifs umount issue, but can't find it at the moment. I did notice that it was a very old bug. If I remember to do "# umount /media/data-srv" before rebooting, all is fine, but I seem to constantly forget and then stew as the system hangs for an extra 30-45 seconds. I've tried several things to automate it including shutdown scripts added to /etc/init.d/ and elsewhere, but nothing seems to work. Anyone have this issue and find a work-around?
If you use the _netdev option, mounting the share will be deferred until the network is ready.
As to the time it takes to unmount, it may depend partly on how the share is mounted and how the device at the server is mounted. The async option allows asyncronous updates & caching. This will improve performance while you are using the device but unsynced data needs to be written to the device before it can be umounted.
30 seconds may be a time-out value for something that is failing. The kernel logs or samba logs may indicate the cause. If you can correct, you may be able to umount the drive quicker.
You might also look at configuring automount. This will automatically mount directories when you enter them and unmount them if you haven't used them for a while. In other words, the directory may be unmounted already, so if you are shutting down for example, you won't have a delay.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.