FreeNAS appears to suffer from Samba bug #8726:
https://bugzilla.samba.org/show_bug.cgi?id=8726
Jeremy Allison @ Samba would like to get in contact with a FreeNAS developer to obtain a backtrace and get this figured out. I'm posting this in hopes of facilitating that.
Basically, if AIO and SMB2 are both enabled, file transfers (especially large ones) fail and smbd crashes:
[2012/10/11 13:31:31.655658, 1] smbd/service.c:1114(make_connection_snum)
vs10 (10.25.2.57) connect to service cifsTest initially as user LEWIS\administrator (uid=20500, gid=20513) (pid 10487)
[2012/10/11 13:32:32.320939, 0] lib/fault.c:51(fault_report)
===============================================================
[2012/10/11 13:32:32.321031, 0] lib/fault.c:52(fault_report)
INTERNAL ERROR: Signal 11 in pid 10487 (3.6.7)
Please read the Trouble-Shooting section of the Samba3-HOWTO
[2012/10/11 13:32:32.321056, 0] lib/fault.c:54(fault_report)
[2012/10/11 13:32:32.321074, 0] lib/fault.c:55(fault_report)
===============================================================
[2012/10/11 13:32:32.321092, 0] lib/util.c:1117(smb_panic)
PANIC (pid 10487): internal error
[2012/10/11 13:32:32.321193, 0] lib/util.c:1221(log_stack_trace)
BACKTRACE: 0 stack frames:
[2012/10/11 13:32:32.321217, 0] lib/util.c:1122(smb_panic)
smb_panic(): calling panic action [/bin/sleep 9999999]
I think this is an issue affecting Samba on FreeBSD in general, as NAS4Free is also affected. I've seen several forum posts for FreeNAS and NAS4Free describing this behavior. I suspect it doesn't come up more because most users don't end up enabling both options.
https://bugzilla.samba.org/show_bug.cgi?id=8726
Jeremy Allison @ Samba would like to get in contact with a FreeNAS developer to obtain a backtrace and get this figured out. I'm posting this in hopes of facilitating that.
Basically, if AIO and SMB2 are both enabled, file transfers (especially large ones) fail and smbd crashes:
[2012/10/11 13:31:31.655658, 1] smbd/service.c:1114(make_connection_snum)
vs10 (10.25.2.57) connect to service cifsTest initially as user LEWIS\administrator (uid=20500, gid=20513) (pid 10487)
[2012/10/11 13:32:32.320939, 0] lib/fault.c:51(fault_report)
===============================================================
[2012/10/11 13:32:32.321031, 0] lib/fault.c:52(fault_report)
INTERNAL ERROR: Signal 11 in pid 10487 (3.6.7)
Please read the Trouble-Shooting section of the Samba3-HOWTO
[2012/10/11 13:32:32.321056, 0] lib/fault.c:54(fault_report)
[2012/10/11 13:32:32.321074, 0] lib/fault.c:55(fault_report)
===============================================================
[2012/10/11 13:32:32.321092, 0] lib/util.c:1117(smb_panic)
PANIC (pid 10487): internal error
[2012/10/11 13:32:32.321193, 0] lib/util.c:1221(log_stack_trace)
BACKTRACE: 0 stack frames:
[2012/10/11 13:32:32.321217, 0] lib/util.c:1122(smb_panic)
smb_panic(): calling panic action [/bin/sleep 9999999]
I think this is an issue affecting Samba on FreeBSD in general, as NAS4Free is also affected. I've seen several forum posts for FreeNAS and NAS4Free describing this behavior. I suspect it doesn't come up more because most users don't end up enabling both options.
