Today I discovered that a second samba server of us is corrupted. The first time when it occurred, I can't recall what I had done. I did too many things at once. But today I didn't do much, I only updated the system clock after that SAMBA panics. Some details of the servers: P4 2.8 512MB, Fedore Core 3, kernel: 2.6.10-1.766_FC3smp. This command (script)I used for setting the clock: #!/bin/bash ntpdate -su 192.168.61.14 hwclock --systohc Samba was still running at time of adjusting. Maybe not so clever I know... anyhow this is the error that now pops up every 2 seconds or so: Mar 16 09:51:50 samba71 nmbd[4187]: [2006/03/16 09:51:50, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(396) Mar 16 09:51:50 samba71 nmbd[4187]: ***** Mar 16 09:51:50 samba71 nmbd[4187]: Mar 16 09:51:50 samba71 nmbd[4187]: Samba name server ES_EINDHOVEN is now a local master browser for workgroup EINDHOVEN on subnet 192.168.71.9 Mar 16 09:51:50 samba71 nmbd[4187]: Mar 16 09:51:50 samba71 nmbd[4187]: ***** Mar 16 08:53:48 samba71 smbd[4354]: [2006/03/16 09:53:48, 0] lib/fault.c:fault_report(36) Mar 16 08:53:48 samba71 smbd[4354]: =============================================================== Mar 16 08:53:48 samba71 smbd[4354]: [2006/03/16 09:53:48, 0] lib/fault.c:fault_report(37) Mar 16 08:53:48 samba71 smbd[4354]: INTERNAL ERROR: Signal 11 in pid 4354 (3.0.10-1.fc3) Mar 16 08:53:48 samba71 smbd[4354]: Please read the appendix Bugs of the Samba HOWTO collection Mar 16 08:53:48 samba71 smbd[4354]: [2006/03/16 09:53:48, 0] lib/fault.c:fault_report(39) Mar 16 08:53:48 samba71 smbd[4354]: =============================================================== Mar 16 08:53:48 samba71 smbd[4354]: [2006/03/16 09:53:48, 0] lib/util.c:smb_panic2(1504) Mar 16 08:53:48 samba71 smbd[4354]: PANIC: internal error Mar 16 08:53:48 samba71 smbd[4354]: [2006/03/16 09:53:48, 0] lib/util.c:smb_panic2(1512) Mar 16 08:53:48 samba71 smbd[4354]: BACKTRACE: 18 stack frames: Mar 16 08:53:48 samba71 smbd[4354]: #0 smbd(smb_panic2+0x8a) [0x69defd] Mar 16 08:53:48 samba71 smbd[4354]: #1 smbd(smb_panic+0x19) [0x69e129] Mar 16 08:53:48 samba71 smbd[4354]: #2 smbd [0x689669] Mar 16 08:53:48 samba71 smbd[4354]: #3 /lib/tls/libc.so.6 [0x867a48] Mar 16 08:53:48 samba71 smbd[4354]: #4 /lib/tls/libc.so.6(getmntent+0x54) [0x900604] Mar 16 08:53:48 samba71 smbd[4354]: #5 smbd [0x586500] Mar 16 08:53:48 samba71 smbd[4354]: #6 smbd(sys_get_quota+0xa1) [0x5866a3] Mar 16 08:53:48 samba71 smbd[4354]: #7 smbd(disk_quotas+0x4f) [0x58b3b9] Mar 16 08:53:48 samba71 smbd[4354]: #8 smbd(sys_disk_free+0xd7) [0x52e931] Mar 16 08:53:48 samba71 smbd[4354]: #9 smbd(vfswrap_disk_free+0x39) [0x5762ff] Mar 16 08:53:48 samba71 smbd[4354]: #10 smbd [0x55f658] Mar 16 08:53:48 samba71 smbd[4354]: #11 smbd(reply_trans2+0xd2b) [0x565753] Mar 16 08:53:48 samba71 smbd[4354]: #12 smbd [0x5818f2] Mar 16 08:53:48 samba71 smbd[4354]: #13 smbd(process_smb+0x195) [0x581d26] Mar 16 08:53:48 samba71 smbd[4354]: #14 smbd(smbd_process+0x15f) [0x582a44] Mar 16 08:53:48 samba71 smbd[4354]: #15 smbd(main+0x865) [0x71ded7] Mar 16 08:53:48 samba71 smbd[4354]: #16 /lib/tls/libc.so.6(__libc_start_main+0xe3) [0x854e33] Mar 16 08:53:48 samba71 smbd[4354]: #17 smbd [0x520231] Exactly the same error we got on server nr.1 couple of days ago. I replaced that server for a new freshly installed server that was the only way to get rid of these errors. All the servers were up for more then a year, without any problems. Strange is also that the nmbd daemon is reporting in the correct time, and the smbd daemon one hour backwards. I rebooted the server 2 times now, removed all the time adjust scripts, even removed the use of UTC time zones. Nothing helped. any suggestions on this case, did I something wrong here or is this a bug ?
The backtrace points to a bug in smbd's quota support which has been fixed. Please retest against the latest release or get RedHat to backport the fix.