[Bug 333695] New: Problems with mount.cifs and umount.cifs
https://bugzilla.novell.com/show_bug.cgi?id=333695 Summary: Problems with mount.cifs and umount.cifs Product: openSUSE 10.3 Version: Final Platform: i686 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: tomrood1@yahoo.com QAContact: qa@suse.de Found By: Customer openSUSE-10.3-GM-GNOME-i386 issues: 1. Unable to auto mount more than the first samba share listed in fstab. 2. When a read-write samba share is mounted, the file browser crashes anytime the folder/share is opened. 3. The system does not shutdown correcly. The Xterminal hangs (after the text shell has been opened) and shows the little timer symbol. openSUSE-10.3-GM-KDE-i386 issues: 1. Unable to auto mount more than the first samba share listed in fstab. 2. Cifs-mount hangs the system when umounting a mounted samba share. 3. If a samba share is mounted, the system will hang on shutdown when terminal the login shows. Logging in again is possible but will not clear the hang. The problems above seem to be related to either cifs-mount or samba-common or the interface between the two. If the smbfs daemon is disabled, the shutdown hang will not occur. mount -t cifs <source1> <destination1> will only work the first time it is executed. mount -t cifs <source2> <destination2> will fail with no error message. The nautilus and konquerer browser seem to handle the samba shares with the smb:// protocol with no difficulties. The samba server in this case is an i686 machine (Dell GX110) running openSUSE 10.2, samba security=share and all shares are guest ok=yes. The commands (and fstab definitions) I used were the same as I have been using in openSUSE 10.2 on the same machine. They worked in openSUSE 10.2 but exhibited the behaviour above in openSUSE 10.3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=333695#c1
--- Comment #1 from Thomas Rood
https://bugzilla.novell.com/show_bug.cgi?id=333695#c2
--- Comment #2 from Thomas Rood
https://bugzilla.novell.com/show_bug.cgi?id=333695
Mark Gordon
https://bugzilla.novell.com/show_bug.cgi?id=333695#c3
Lars Müller
https://bugzilla.novell.com/show_bug.cgi?id=333695#c4
Matthias Koenig
https://bugzilla.novell.com/show_bug.cgi?id=333695#c5
Thomas Rood
https://bugzilla.novell.com/show_bug.cgi?id=333695#c6
Matthias Koenig
https://bugzilla.novell.com/show_bug.cgi?id=333695
User jeffm@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=333695#c9
Jeff Mahoney
https://bugzilla.novell.com/show_bug.cgi?id=333695
User gregkh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=333695#c10
Greg Kroah-Hartman
https://bugzilla.novell.com/show_bug.cgi?id=333695
User lmuelle@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=333695#c11
--- Comment #11 from Lars Müller
https://bugzilla.novell.com/show_bug.cgi?id=333695
User tomrood1@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=333695#c12
--- Comment #12 from Thomas Rood
participants (1)
-
bugzilla_noreply@novell.com