[Samba] Internal error-Panic
Hi, We are running a samba server ( Version 3.0.10-1.4E.6.2 ) on a redHat RHEL release 4 (Nahant Update 3). We have a lot of errors that occurs when windowsXP clients hosts try to read from a Samba Export. We can't upgrade the Samba version because we are blocked by RHEL releases. This is the log returned by the smb server : [2006/09/22 13:53:22, 0] lib/fault.c:fault_report(36) === [2006/09/22 13:53:22, 0] lib/fault.c:fault_report(37) INTERNAL ERROR: Signal 7 in pid 22609 (3.0.10-1.4E.6.2) Please read the appendix Bugs of the Samba HOWTO collection [2006/09/22 13:53:22, 0] lib/fault.c:fault_report(39) === [2006/09/22 13:53:22, 0] lib/util.c:smb_panic2(1504) PANIC: internal error [2006/09/22 13:53:22, 0] lib/util.c:smb_panic2(1512) BACKTRACE: 16 stack frames: #0 smbd(smb_panic2+0x8a) [0xe44260] #1 smbd(smb_panic+0x19) [0xe4448c] #2 smbd [0xe30bff] #3 /lib/tls/libc.so.6 [0x6858e8] #4 smbd [0xe57d0d] #5 smbd [0xe582fe] #6 smbd(tdb_store+0x137) [0xe59426] #7 smbd(set_share_mode+0x1d3) [0xe00f09] #8 smbd(open_file_shared1+0xde2) [0xd1be6d] #9 smbd(reply_ntcreate_and_X+0x88f) [0xceefa8] #10 smbd [0xd2d4c2] #11 smbd(process_smb+0x19b) [0xd2d8fc] #12 smbd(smbd_process+0x15f) [0xd2e624] #13 smbd(main+0x875) [0xec0b37] #14 /lib/tls/libc.so.6(__libc_start_main+0xd3) [0x672e23] #15 smbd [0xccd231] thanks for helping me to undestand what occurs and what these logs means. Jonathan -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] closewait socket state
I have a probleme with my samba server. I have a lot of closewait socket state causing the load average to increase. Samba generate some errors logs but I don't know the signification of Signal 7 in pid xxx. For information, I am running a samba 3.0.10-1.4E.2 under a kernel Linux version 2.6.9-22 with a RHEL 3.4.4-2. Here is the log file (/var/log/messages) : -- Jul 11 13:56:33 linuxd smbd[8481]: yield_connection: tdb_delete for name J failed with error Record does not exist. Jul 11 13:56:33 linuxd smbd[27341]: [2006/07/11 13:56:33, 0] lib/util_sock.c:write_socket_data(430) Jul 11 13:56:33 linuxd smbd[19620]: [2006/07/11 13:56:33, 0] smbd/connection.c:yield_connection(76) Jul 11 13:56:33 linuxd smbd[27341]: write_socket_data: write failure. Error = Broken pipe Jul 11 13:56:33 linuxd smbd[8408]: [2006/07/11 13:56:33, 0] lib/util_sock.c:write_socket_data(430) Jul 11 13:56:33 linuxd smbd[27341]: [2006/07/11 13:56:33, 0] smbd/connection.c:yield_connection(76) Jul 11 13:56:33 linuxd smbd[8489]: [2006/07/11 13:56:33, 0] smbd/connection.c:yield_connection(76) [...] 1 13:56:33 linuxd smbd[17231]: write_socket_data: write failure. Error = Broken pipe Jul 11 13:56:33 linuxd smbd[16632]: write_socket_data: write failure. Error = Broken pipe Jul 11 13:56:33 linuxd smbd[8410]: write_socket_data: write failure. Error = Broken pipe Jul 11 13:56:33 linuxd smbd[2542]: oplock_break: end of file from client Jul 11 13:56:33 linuxd smbd[13744]: write_socket_data: write failure. Error = Broken pipe Jul 11 13:56:33 linuxd smbd[27841]: write_socket_data: write failure. Error = Connection reset by peer Jul 11 13:56:33 linuxd smbd[8484]: write_socket_data: write failure. Error = Broken pipe [...] ul 11 13:56:37 linuxd smbd[9455]: Error writing 134 bytes to client. -1. (Broken pipe) Jul 11 13:56:37 linuxd smbd[8980]: Error writing 58 bytes to client. -1. (Broken pipe) Jul 11 13:56:37 linuxd smbd[8963]: Error writing 58 bytes to client. -1. (Broken pipe) Jul 11 13:56:37 linuxd smbd[14781]: [2006/07/11 13:56:37, 0] lib/fault.c:fault_report(39) Jul 11 13:56:37 linuxd smbd[10470]: Error writing 58 bytes to client. -1. (Broken pipe) Jul 11 13:56:37 linuxd smbd[8706]: Error writing 134 bytes to client. -1. (Broken pipe) Jul 11 13:56:37 linuxd smbd[9066]: Error writing 134 bytes to client. -1. (Broken pipe) Jul 11 13:56:37 linuxd smbd[9450]: Error writing 134 bytes to client. -1. (Broken pipe) Jul 11 13:56:37 linuxd smbd[8715]: Error writing 134 bytes to client. -1. (Broken pipe) [...] Jul 11 13:56:37 linuxd smbd[14781]: BACKTRACE: 16 stack frames: Jul 11 13:56:37 linuxd smbd[9074]: BACKTRACE: 20 stack frames: Jul 11 13:56:37 linuxd smbd[16632]: yield_connection: tdb_delete for name H failed with error Record does not exist. Jul 11 13:56:37 linuxd smbd[14781]:#0 smbd(smb_panic2+0x8a) [0xe9fe90] Jul 11 13:56:37 linuxd smbd[9074]:#0 smbd(smb_panic2+0x8a) [0xe9fe90] Jul 11 13:56:37 linuxd smbd[14781]:#1 smbd(smb_panic+0x19) [0xea00bc] Jul 11 13:56:37 linuxd smbd[9074]:#1 smbd(smb_panic+0x19) [0xea00bc] Jul 11 13:56:37 linuxd smbd[14781]:#2 smbd [0xe8c80f] Jul 11 13:56:37 linuxd smbd[9074]:#2 smbd [0xe8c80f] Jul 11 13:56:37 linuxd smbd[14781]:#3 /lib/tls/libc.so.6 [0x3f38c8] Jul 11 13:56:37 linuxd smbd[9074]:#3 /lib/tls/libc.so.6 [0x3f38c8] Jul 11 13:56:37 linuxd smbd[14781]:#4 smbd [0xeb393d] Jul 11 13:56:37 linuxd smbd[9074]:#4 smbd [0xeb393d] Jul 11 13:56:37 linuxd smbd[14781]:#5 smbd [0xeb3f2e] Jul 11 13:56:37 linuxd smbd[9074]:#5 smbd [0xeb3f2e] Jul 11 13:56:37 linuxd smbd[14781]:#6 smbd(tdb_store+0x137) [0xeb5056] Jul 11 13:56:37 linuxd smbd[9074]:#6 smbd(tdb_store+0x137) [0xeb5056] Jul 11 13:56:37 linuxd smbd[14781]:#7 smbd(set_share_mode+0x1d3) [0xe5cd19] Jul 11 13:56:37 linuxd smbd[9074]:#7 smbd(claim_connection+0x252) [0xd35b16] Jul 11 13:56:37 linuxd smbd[14781]:#8 smbd(open_file_shared1+0xde2) [0xd77dfd] Jul 11 13:56:37 linuxd smbd[9074]:#8 smbd [0xd8b539] Jul 11 13:56:37 linuxd smbd[14781]:#9 smbd(reply_ntcreate_and_X+0x88f) [0xd4af38] Jul 11 13:56:37 linuxd smbd[9074]:#9 smbd(make_connection+0x162) [0xd8ca54] Jul 11 13:56:37 linuxd smbd[14781]:#10 smbd [0xd89412] Jul 11 13:56:37 linuxd smbd[9074]:#10 smbd(reply_tcon_and_X+0x1d3) [0xd52bb6] Jul 11 13:56:37 linuxd smbd[14781]:#11 smbd(process_smb+0x19b) [0xd8984c] Jul 11 13:56:37 linuxd smbd[9074]:#11 smbd [0xd89412] Jul 11 13:56:37 linuxd smbd[14781]:#12 smbd(smbd_process+0x15f) [0xd8a574] Jul 11 13:56:37 linuxd smbd[9074]:#12 smbd(chain_reply+0x178) [0xd89cb8] Jul 11 13:56:37 linuxd smbd[14781]:#13 smbd(main+0x865) [0xf1c567] Jul 11 13:56:37 linuxd smbd[9074]:#13 smbd(reply_sesssetup_and_X+0xabe) [0xd62feb] Jul 11 13:56:37 linuxd smbd[14781]:#14 /lib/tls/libc.so.6(__libc_start_main+0xd3) [0x3e0e23] Jul 11 13:56:37 linuxd smbd[9074]:#14 smbd [0xd89412] Jul 11 13:56:37 linuxd smbd[14781]:#15 smbd
[Samba] unknown UDP message
Hi, I have some serious problem with my Samba server in production environment. For information, I am running a samba 3.0.10-1.4E.2 under a kernel Linux version 2.6.9-22 with a RHEL 3.4.4-2. The problem is that I noticed in the log files the following errors : smbd[25842]: [2006/06/14 11:25:07, 0] smbd/oplock.c:request_oplock_break(1055) smbd[25842]: request_oplock_break: no response received to oplock break request to pid 25225 on port 33355 for dev = 16, inode = 4720682, file_id = 2 Next ... 3 hours later another error appear : smbd[25842]: process_local_message: unknown UDP message command code (8003) - ignoring. smbd[25842]: [2006/06/14 15:00:40, 0] smbd/oplock.c:process_local_message(441) And this last one occured more than 200 times per seconds during 4 seconds and pull the CPU to 100 percent, with a smbd process at 99% : 25842 nobody25 0 12864 3740 3112 R 99.7 0.1 10053:47 smbd By the way, since this time samba connections seems anormaly slow ... So does anyone know something about this problem ? Is there a way to avoid this ? thanks -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba on NAS perfs
Hi, I am running a samba 3.0.14a server on a 2.6.15.6 kernel, on a 4T - SATA2 NAS. The disks are formated in xfs and configurated in hard RAID5. Network is bonded with 2 Gbits links using 802.3ad agregation. The NAS is connected on a Gbits switch (Summit 400 - extreme Networks), also configured with dynamic sharing. I am trying to get the best performances in Reading/writting the NAS, and what I am obtaining is very poor ... I have been trying many kind of tests with several clients (win XP console, win XP gui, MACOSX, many linux ...). The fact is first I can't get the first NAS interface overloaded, it never get the turn to the second one. I have very poor transfer rates : -copy to windows from a NAS Samba export : max 20 MBytes/s with many kind of file sizes -copy to Linux (on firewire 800) from a NAS Samba export : max 12 MBytes/s with many kind of file sizes The linux mount is made using CIFS drivers. on the other side, writting on the NAS give me the same results. I have also made some tests with the IOMeter tool on a winXP samba mount, configure with a transfert request size of 32MB, 100% reading, full sequential access. With 4 workers on the same client I get (according to snmp results) a rate of 80 MBytes/s ! PS : Directly on the NAS, using the tool Bonnie++ (not using samba...) we get a pretty 150 MBytes/s with the writting tests. PS2 : We have made theses tests with samba,nfs and Afp exports The clients configurations are the following : - linux clients : Bi-Proc 1Ghz - 1 GB RAM Disks Firewire 800 GbE network - Avid HP WinXP Bi-Proc 3Ghz 2GB RAM 6 SCSI RAID0 drives GbE network Thanks for helping me to understand why we can't get better perfs ? john -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
