id,summary,reporter,owner,description,type,status,priority,milestone,component,version,resolution,keywords,cc 215,Samba 3.5.x smbd and nmbd both trash tdb files after some time,Herwig Bauernfeind,Silvan Scherrer,"Symptoms: 3.5.19 nmbd stops working after some arbitrary time. For smbd no mor new connection is accepted, while older one still work. Looking into log.nmbd I see plenty of these: {{{ [2013/03/15 11:40:54.862000, 0] lib/util_tdb.c:385(tdb_log) tdb(D:\MPTN\ETC/samba/lock/wins.tdb): tdb_rec_read bad magic 0xd9fee666 at offset=6392 [2013/03/15 11:40:54.888000, 0] lib/util_tdb.c:385(tdb_log) tdb(D:\MPTN\ETC/samba/lock/wins.tdb): tdb_rec_read bad magic 0x42424242 at offset=5384 [2013/03/15 11:40:54.925000, 0] lib/util_tdb.c:385(tdb_log) tdb(D:\MPTN\ETC/samba/lock/wins.tdb): tdb_oob len 1113543791 beyond eof at 24576 [2013/03/15 11:40:54.925000, 0] lib/util_tdb.c:385(tdb_log) tdb(D:\MPTN\ETC/samba/lock/wins.tdb): tdb_rec_read bad magic 0x0 at offset=6704 }}} for smbd.exe log entries look very similar. Result is: nmbd.exe process is unkillable and smbd does not accept any new connection. This problem also affects the client. ",defect,closed,blocker,Samba Server for eCS (OS/2) 1.3.x,Samba Server Core,Server 3.5.x,wontfix,unkillable broken tdb files,