Opened 13 years ago

Closed 13 years ago

#186 closed defect (duplicate)

smbd blocks after 25.000 files

Reported by: Leo123 Owned by: Silvan Scherrer
Priority: critical Milestone: Samba Server for eCS (OS/2) 1.1.x
Component: Samba Server Version: Server 3.3.x
Keywords: Cc:

Description

I am trying to use Samba for the backup of my system. I use a scsi tapedrive in a client for that. The samba server get into problems after about 25.000 files. I get:

From log.smbd.leo.10.0.0.153:

Killed by SIGFPE pid=0x00bb ppid=0x008a tid=0x0001 slot=0x00c0 pri=0x0400 mc=0x0001 D:\PROGRAMS\SAMBA\SMBD.EXE LIBC064X 0:00035096 cs:eip=005b:11125096 ss:esp=0053:0061f240 ebp=0061f278

ds=0053 es=0053 fs=150b gs=0000 efl=00010293

eax=00000000 ebx=00000000 ecx=0061f260 edx=00000018 edi=113d8a10 esi=00000000 Process dumping was disabled, use DUMPPROC / PROCDUMP to enable it. -toezichthouders/slides/P3270104.JPG read=Yes write=No (numopen=1) [2012/02/01 14:52:03, 1] lib/util_tdb.c:tdb_wrap_log(886)

tdb(D:\MPTN\ETC\samba\lock/locking.tdb): tdb_lock failed on list -1 ltype=3 (Invalid argument)

[2012/02/01 14:52:03, 0] locking/locking.c:share_mode_lock_destructor(747)

store returned NT_STATUS_UNSUCCESSFUL

[2012/02/01 14:52:03, 0] lib/util.c:smb_panic(1686)

PANIC (pid 391): could not store share mode entry

[2012/02/01 14:52:03, 0] lib/util.c:log_stack_trace(1840)

unable to produce a stack trace on this platform

[2012/02/01 14:52:03, 0] lib/fault.c:dump_core(235)

dumping core in D:\MPTN\ETC/samba/log/cores/smbd

Killed by SIGABRT pid=0x0187 ppid=0x008a tid=0x0001 slot=0x00b4 pri=0x0400 mc=0x0001 D:\PROGRAMS\SAMBA\SMBD.EXE Process dumping was disabled, use DUMPPROC / PROCDUMP to enable it. [2012/02/01 14:52:06, 2] auth/auth.c:check_ntlm_password(308)

and so on.

I canot find anyting about this in the samba info on www.samba.org so it may be abug in the eCS version of smbd.exe

Greetings Leo Koelemij

Change History (1)

comment:1 by Herwig Bauernfeind, 13 years ago

Resolution: duplicate
Status: newclosed

This Ticket is a dupliate of Ticket #187

Note: See TracTickets for help on using tickets.