> Hi, > > My Samba box stalls after some usage, mapped drives disappear and users > can't write or read from drives. The stalls happen randomly. I'm running > 2.4.19-16mdksmp and Samba 2.2.7a-9.2mdk. May I ask is this a kernel bug > or Samba bug? Does anyone know a fix for it? I checked the memory from > BIOS, they didn't report any errors.
BIOS memory check is (mostly) useless. Use memtest86 or similar. Also, your kernel seems a bit behind, I think current on 9.0 is 2.4.19-32mdk (though I don't think this should make that much difference). > > /var/log/kernel/warnings > ------------------------ > Oct 27 09:19:12 smbserver kernel: xfs_force_shutdown(md(9,5),0x8) called > from line 1039 of file xfs_trans.c. Return address = 0xe08ae312 > Oct 27 09:19:12 smbserver kernel: Corruption of in-memory data detected. > Shutting down filesystem: md(9,5) > Oct 27 09:19:12 smbserver kernel: Please umount the filesystem, and > rectify the problem(s) This seems to point quite strongly to either hardware (most likely memory) or kernel (xfs driver or md driver, it seems you are running software raid?) If the kernel has problems with a filesystem, there's nothing much samba can do about it ... > > /var/log/kernel/errors > ---------------------- > Oct 27 10:36:44 smbserver kernel: Unknown bridge resource 2: assuming > transparent > Oct 27 10:36:44 smbserver kernel: PCI: Unable to handle 64-bit address > space for > Oct 27 10:36:44 smbserver kernel: PCI: Unable to handle 64-bit address > space for > Oct 27 10:36:44 smbserver kernel: Unknown bridge resource 2: assuming > transparent > Oct 27 10:36:44 smbserver kernel: PCI: Device 00:1f.1 not available > because of resource collisions You need to give some more information on the hardware on this machine, but something does not look right ... what's in /proc/interrupts ? > > /var/log/samba/log.winbindd > --------------------------- > [2003/10/27 10:37:23, 0] nsswitch/winbindd.c:process_loop(626) > process_loop: Invalid request size (1701996389) sent, should be (1304) Some winbind users have reported winbind in 2.2.8a works a bit better, you can find packages on the samba FTP mirrors for all supported releases (hmm, except ldap-enabled packages for 9.2 ... I must do this still ...). BTW: [EMAIL PROTECTED] bgmilne]$ cat /etc/mandrake-release Mandrake Linux release 9.0 (dolphin) for i586 [EMAIL PROTECTED] bgmilne]$ uname -r 2.4.19-32mdksecure [EMAIL PROTECTED] bgmilne]$ uptime 11:26pm up 165 days, 6:00, 1 user, load average: 0.01, 0.02, 0.00 [EMAIL PROTECTED] bgmilne]$ rpm -qa 'samba*' samba3-common-3.0.0-1.1mdk samba-server-ldap-2.2.8a-2mdk samba3-server-3.0.0-1.1mdk samba-common-ldap-2.2.8a-2mdk samba-client-2.2.8a-2mdk (This is our production samba domain controller for about 60 concurrent users, with 100GB of data shared on XFS over LVM on hardware RAID - never have problems with it). Regards, Buchan
