Re: miata and samba3

On Fri, February 11, 2005 16:51, Edwin Barendse said:
[snip]
> The problem I run into is with Samba (3.0.9-r1 as well 3.0.10) it
> compiles well (fails on smbtorture, but ok) runs fine and seems oke but
> when trying to place a file on the fileshare ,for a windows client, it
> fails warning about the network name no longer available, still creates
> an empty file, when looking in the log file it states a INTERNAL ERROR
> Signal 11 and stating it should be submitted as a bug, but with the same
> system running on a dual-xeon no problem.

You mean like this (from /var/log/messages):

Feb 12 13:15:40 alf smbd[11608]: [2005/02/12 13:15:40, 0]
lib/fault.c:fault_report(36)
Feb 12 13:15:40 alf smbd[11608]:  
===============================================================
Feb 12 13:15:40 alf smbd[11608]: [2005/02/12 13:15:40, 0]
lib/fault.c:fault_report(37)
Feb 12 13:15:40 alf smbd[11608]:   INTERNAL ERROR: Signal 11 in pid 11608
(3.0.2a)
Feb 12 13:15:40 alf smbd[11608]:   Please read the appendix Bugs of the
Samba HOWTO collection
Feb 12 13:15:40 alf smbd[11608]: [2005/02/12 13:15:40, 0]
lib/fault.c:fault_report(39)
Feb 12 13:15:40 alf smbd[11608]:  
===============================================================
Feb 12 13:15:40 alf smbd[11608]: [2005/02/12 13:15:40, 0]
lib/util.c:smb_panic(1400)
Feb 12 13:15:40 alf smbd[11608]:   PANIC: internal error
Feb 12 13:15:40 alf smbd[11608]: [2005/02/12 13:15:40, 0]
lib/util.c:smb_panic(1408)
Feb 12 13:15:40 alf smbd[11608]:   BACKTRACE: 0 stack frames:
Feb 12 13:15:40 alf smbd[11608]:

As you can probably tell from the above, I have the same problem on my
XLT-300... One way in which the problem manifests itself is when I try to
create a new folder on the Samba share from a Windows 2000 machine (I did
this to get the log messages shown above). W2k complains about "New
Folder" already existing, which is not true; it creates a directory named
"New Folder" and does not give me the chance to specify a name. Copying
files using ctrl-C/ctrl-V also does not work properly, but using
drag-and-drop does work. Strange...

This is for samba-3.0.2a-r2, I'll try to upgrade to a newer version
although I fear the problem will not go away (as Edwin did try with a
newer version).

BTW, my entire setup was built with CFLAGS="-mcpu=ev5 -mieee -O2 -pipe"

Marnix.


--
[email protected] mailing list