I just upgraded both my server and my client; now, I can’t mount the samba shares on the server any more!
What basically happened first is that I just could not access them – after being inside one and doing simple stuff like “ls” (or browsing into one from a normal file dialog), the system hang – and after a long time, I got an “input/output error”.
Issueing a “mount -a” (after all, the mountpoints of the shares are defined in the client’s /etc/fstab) resulted in an ERRnosuchshare error.
I googled around, and first thing I did was chaning the file system on the client’s /etc/fstab from smbfs to cifs (see this blog entry for my entire samba configuration!). This did not help; “mount -a” did not yield any error messages any more, but still, after changing to one of the mount-points of a share and issueing a simple “ls”, same error.
When I then looked into the (server’s) log files, I noticed this:
[2007/11/17 16:38:26, 0] lib/util.c:smb_panic(1632)
PANIC (pid 12987): push_ascii - dest_len == -1
[2007/11/17 16:38:26, 0] lib/util.c:log_stack_trace(1736)
BACKTRACE: 1 stack frames:
#0 /usr/sbin/smbd(log_stack_trace+0x29) [0x8020d51a]
[2007/11/17 16:38:26, 0] lib/fault.c:dump_core(181)
dumping core in /var/log/samba/cores/smbd
Googling for the panic error, I stumbled finally across this resource – it’s a bug entry related to Ubuntu, but I assume it’s the exact error I encounter. On forums.gentoo.org, I then found this entry; after searching on bugs.gentoo.org, I could not find a related bug, so I opened one.
In the meantime, I downgraded back to samba-3.0.26a (i. e. I masked samba >= 3.0.27 in /etc/portage/package.mask) – everything works fine here…
