Red Hat Bugzilla – Bug 1435
umount fails on SMB mounted filesystems.
Last modified: 2016-05-17 13:28:01 EDT
I'm running kernel 2.2.2, RH 5.2, and have installed the recent kernel 2.2 update rpms. Upon reboot, the halt script stops at the umount command. It appears that the current version of umount does not support smb mounted filesystems. This caused severe data loss on my system.
what version of mount are you running? ------- Email Received From Joshua Weage <gte855f@prism.gatech.edu> 03/22/99 19:05 -------
can you grab the mount-2.9 SRPM from Raw Hide/Starbuck and recompile it and see if that works? If so, we'll put it in the kernel-2.2 RPMS stuff. ------- Email Received From Joshua Weage <gte855f@prism.gatech.edu> 03/22/99 20:43 ------- ------- Email Received From Joshua Weage <gte855f@prism.gatech.edu> 03/23/99 08:52 -------
I'm looking into why it's hanging; umount -a at the end *should* work, especially since it works everywhere else...
Bugger. umounting smb filesystems hangs if there's no network. Looking into patching the kernel to support umount -f for smb.
The fix, for now, is to add a line to the nfsfs startup script, in the stop section, that says 'umount -a -t smbfs'. This will be fixed in the next initscripts release, which will have a 'netfs' script that mounts and unmounts network filesystems (smb, ncp, nfs.) (Eventually, we'll get the kernel fixed so that you can forcefully umount a SMB share even if the network goes away.)
Commit pushed to master at https://github.com/openshift/openshift-ansible https://github.com/openshift/openshift-ansible/commit/fc33fa4733d95aa32a2844ac4d802aad9830e610 Merge pull request #1897 from sdodson/issue1435 Include sdn-ovs in upgrade commands to avoid pulling in newer packages