SMB3 Errors

[loozhengyuan]

Hi all. I've been wanting to post this but kept procrastinating. So basically, ever since I updated to FreeBSD 10 and then upgrading from SMB2 to SMB3, one of my NAS started to have this problem. I tried replicating this problem on another NASes, but i can't seem to do it. I've also tried the kernel change notify = no parameter, but it doesn't work too. I've also waited for 'bugs' to smoothen out over time hoping that it would solve the problem, but it still persists. I'm currently on 10.2.0.2 - Prester (revision 2235). So here are error logs that keep repeating itself almost everyday. Let me know if there's anything that I can do.

Code: Select all

Jan 16 16:46:18	smbd[8754]:	refusing to dump core
Jan 16 16:46:18	smbd[8754]:	unable to change to %N.core
Jan 16 16:46:18	smbd[8754]:	[2016/01/16 16:46:18.062502, 0] ../source3/lib/dumpcore.c:313(dump_core)
Jan 16 16:46:18	smbd[8754]:	#5 0x80145c1a8 <pthread_getspecific+0xdd8> at /lib/libthr.so.3
Jan 16 16:46:18	smbd[8754]:	#4 0x80145c9aa <pthread_sigmask+0x4aa> at /lib/libthr.so.3
Jan 16 16:46:18	smbd[8754]:	#3 0x80168e9b7 <fault_setup+0x157> at /usr/local/lib/libsamba-util.so.0
Jan 16 16:46:18	smbd[8754]:	#2 0x80168eb0d <smb_panic+0x13d> at /usr/local/lib/libsamba-util.so.0
Jan 16 16:46:18	smbd[8754]:	#1 0x8035c2832 <smb_panic_s3+0x52> at /usr/local/lib/libsmbconf.so.0
Jan 16 16:46:18	smbd[8754]:	#0 0x8035c2948 <log_stack_trace+0x28> at /usr/local/lib/libsmbconf.so.0
Jan 16 16:46:18	smbd[8754]:	BACKTRACE: 6 stack frames:
Jan 16 16:46:18	smbd[8754]:	[2016/01/16 16:46:18.062437, 0] ../source3/lib/util.c:899(log_stack_trace)
Jan 16 16:46:18	smbd[8754]:	PANIC (pid 8754): internal error
Jan 16 16:46:18	smbd[8754]:	[2016/01/16 16:46:18.061757, 0] ../source3/lib/util.c:788(smb_panic_s3)
Jan 16 16:46:18	smbd[8754]:	===============================================================
Jan 16 16:46:18	smbd[8754]:	[2016/01/16 16:46:18.061745, 0] ../lib/util/fault.c:81(fault_report)
Jan 16 16:46:18	smbd[8754]:	Please read the Trouble-Shooting section of the Samba HOWTO
Jan 16 16:46:18	smbd[8754]:	INTERNAL ERROR: Signal 11 in pid 8754 (4.2.6)
Jan 16 16:46:18	smbd[8754]:	[2016/01/16 16:46:18.061727, 0] ../lib/util/fault.c:79(fault_report)
Jan 16 16:46:18	smbd[8754]:	===============================================================
Jan 16 16:46:18	smbd[8754]:	[2016/01/16 16:46:18.061670, 0] ../lib/util/fault.c:78(fault_report)

Here are the self-multiplying 'guest' users from the same IP address. (can get up to 100 'guest' users from same IP)



Here are my settings for SMB

[loozhengyuan]

Anybody has any ideas?

[b0ssman]

whats your hardware?
are you running the embedded install?
do you have swap enabled?

[loozhengyuan]

Here is what you need:

[b0ssman]

can you run a 24h memtest?

[loozhengyuan]

Okay, will do and update soon.

[raulfg3]

Some users report simmilar errors when update , and where gone in a fresh install.

Please try to save your config, do a new fresh install and restore config

[spy0r]

Some users report simmilar errors when update , and where gone in a fresh install.

Please try to save your config, do a new fresh install and restore config

yes! i had the same issues after upgrading through some revisions - they were gone after reinstalling and restoring config!

[loozhengyuan]

oh! okay, thank you raulfg3 and spy0r, i will try that!!

[loozhengyuan]

Just an update,

I reinstalled already but it seems that the errors are still persistent. Hmmm.

[raulfg3]

sorry, as a workarround, try to use SMB2 as max protocol, and do some test.

in my real emviroment I do not notice any speed improvement to use SMB3, so finally I use SMB2.

[Jack Foobar]

SMB3 is primarily for use with Windows 10 OS's. Everyone else uses SMB2. There is no speed improvement. SMB2 pegs the meter for me across Gig-E. If you do have a Windows 10 machine, you can modify the registry so that it can see the SMB2 protocol.

If you can't solve it, route around it. There is no brass ring for using SMB3, especially with all of that trouble.

[kenZ71]

Given how many people complain about samba would think there would be an alternative

I've tried using sftp for my Amazon Fire / Kodi boxes & my android phone with ES File Explorer, it works for those but not great for speed.