http://bugzilla.novell.com/show_bug.cgi?id=612660 http://bugzilla.novell.com/show_bug.cgi?id=612660#c0 Summary: [SMBTA] stress test smbtad @ hackweek Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: Other Status: ASSIGNED Severity: Normal Priority: P5 - None Component: Samba AssignedTo: mhaefner@novell.com ReportedBy: hhetter@novell.com QAContact: samba-maintainers@SuSE.de CC: bbrunner@novell.com Found By: --- Blocker: --- There is a specific situation where I suspect a deadlock/hang of smbtad (not a crash), and I think this is related to the sqlite handling. This causes the samba server to timeout the connection. To get this fixed and analyzed, I propose: 1. run a smbtatorture session with really large volume, e.g. with a 16 GB file set, and record the session to a file, and take the time. ( run this session on our NEW server, and NOT on seizewell, because seizewell doesn't have enough storage) 2. first run should be WITHOUT the module at all. The pure samba server. 3. look at the behaviour. 4. run the same smbtatorture session with playback, with the module ENABLED. 5. look at the behaviour. On the second run, check the logs of smbtad. AI Holger add debugging messages to the sqlite handling. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.