http://bugzilla.novell.com/show_bug.cgi?id=517768
http://bugzilla.novell.com/show_bug.cgi?id=517768#c10
--- Comment #10 from Gernot Hillier 2009-11-27 12:16:37 UTC ---
And the 3rd problem caused by these scripts: if any process still has a file
opened on a CIFS share, you'll experience a long hang during shutdown triggered
by the call to smbfs in ifdown:
---
Shutting down network time protocol daemon (NTPD) done
Umount SMB/ CIFS File Systems .unmount error 16 = Device or resource busy
Refer to the umount.cifs(8) manual page (man 8 umount.cifs)
done
Shutting down syslog services done
Shutting down (localfs) network interfaces:
eth0 device: Broadcom Corporation NetXtreme BCM5780 Gigabit Ethernet
(rev 10)
tg3 0000:04:04.0: PME# enabled
tg3 0000:04:04.0: wake-up capability enabled by ACPI done
eth1 device: Broadcom Corporation NetXtreme BCM5780 Gigabit Ethernet
(rev 10)
No configuration found for eth1
Nevertheless the interface will be shut down.
CIFS VFS: No response for cmd 50 mid 51897
---
The last line above comes from the smbfs script magically called by "ifdown
eth1". This causes network accesses via the still-mounted CIFS share despite
the fact that eth0 is already down and so no answer can be received.
At this point, shutdown will hang for a long time until a CIFS timeout occurs
finally letting the shutdown proceed.
Removing /etc/sysconfig/network/if-{up,down}.d/21-smbfs also fixed this.
So I'd again really recommend to removing this magic...
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.