Hello all, I've been reading up on the posts and help offered here on the forum and I've already learned a lot about FreeNAS compared to a month and a half ago when I decided to make the move over (still definitely a noob to FreeNAS and FreeBSD though). I've read up on recommended CIFS config in the FreeNAS documentation and on previous posts as to issues with CIFS share write performance issues, but I've run out of ideas (not that I had many to begin with) and I've tried as many solutions as I could find from previous posts.
Basically, I'm getting timeout issues when trying to transfer large junks of data - around 1TB - FreeNAS will write about 5-10GB of data and then timeout for about 30 seconds before transferring another 5-10GB. I keep seeing the following message in the console message area of the WebGUI: STATUS=daemon 'smbd' finished starting up and ready to serve connectionsfany (ipv4:192.168.1.104:62481) closed connection to service Media
The timeout happens even in the middle of files and sometimes causes the file to be skipped. Additionally, even when the transfer is actually moving data, I'm only seeing write speeds of about 35-40 MB/s.
My FreeNAS setup is as follows:
OS Version: FreeNAS-9.3-STABLE-201511020249
Chasis: SuperMicro SSG-6048R-E1CR36N
Motherboard: SuperMicro Super X10DRi-T4+
CPUs: 2 Intel Xeon E5-2680v3
RAM: 128GB Kingston ECC DDR4 2133 (8 16GB DIMMS)
NICS: Onboard Quad Intel 10GBase-T X540 (Static Assigned IPs)
HBA: SuperMicro LSI 2308 HBA (IT firmware version 19, driver version 20 in FreeNAS)
OS HDDs: Mirrored Samsung 850 500GB SSDs
ZFS HDDs: 12x Hitachi 8TB Ultrastar SATA Drives in RAIDZ2
The server sending data to the FreeNAS box is a node from a Dell C6100 with 2 Intel Xeon L5520 CPUs, 72GB ECC DDR3 RAM and Dual 1GB Intel NICs running Windows 8.1. I've consistently written to the Dell at a little less than 200MB/s in the past and read speeds are even faster, so I don't think the Dell is the bottleneck. The two machines are connected through an HP 2920-48G switch without LACP setup on the particular ports. However, the switch has no issue transferring at speeds much higher than 40MB/s.
After reading numerous other posts about write speed issues with CIFS shares, I've disabled Hyperthreading in the BIOS settings and have added the following Auxiliary Parameters to my CIFS service config:
ea support = no
store dos attributes = no
map archive = no
map hidden = no
map readonly = no
map system = no
I also have local master disabled and I've enabled UNIX extensions, with the server maximum protocol set for SMB3_00. Disabling Hyperthreading has seemed to help a bit with the write speed, but not much (maybe a 5-10MB/s increase - I was getting transfer speeds below 30MB/s before), but I'm still getting the same timeout issue. I do have encryption enabled on my pool along with AES-NI enabled on the CPUs in the BIOS.
Another odd, but maybe unrelated, issue is that when I disabled Hyperthreading a couple days ago I also enabled x2APIC in the CPU BIOS settings which subsequently kept causing a "kernel trap 12 with interrupts disabled" error at FreeNAS startup. As soon as I disabled x2APIC, FreeNAS booted up normally - I tested my CPU and RAM and both came back normal.
Any guidance would be greatly appreciated and thanks for all the information that is generally available through this community - it's already proven to be an invaluable resource.
Basically, I'm getting timeout issues when trying to transfer large junks of data - around 1TB - FreeNAS will write about 5-10GB of data and then timeout for about 30 seconds before transferring another 5-10GB. I keep seeing the following message in the console message area of the WebGUI: STATUS=daemon 'smbd' finished starting up and ready to serve connectionsfany (ipv4:192.168.1.104:62481) closed connection to service Media
The timeout happens even in the middle of files and sometimes causes the file to be skipped. Additionally, even when the transfer is actually moving data, I'm only seeing write speeds of about 35-40 MB/s.
My FreeNAS setup is as follows:
OS Version: FreeNAS-9.3-STABLE-201511020249
Chasis: SuperMicro SSG-6048R-E1CR36N
Motherboard: SuperMicro Super X10DRi-T4+
CPUs: 2 Intel Xeon E5-2680v3
RAM: 128GB Kingston ECC DDR4 2133 (8 16GB DIMMS)
NICS: Onboard Quad Intel 10GBase-T X540 (Static Assigned IPs)
HBA: SuperMicro LSI 2308 HBA (IT firmware version 19, driver version 20 in FreeNAS)
OS HDDs: Mirrored Samsung 850 500GB SSDs
ZFS HDDs: 12x Hitachi 8TB Ultrastar SATA Drives in RAIDZ2
The server sending data to the FreeNAS box is a node from a Dell C6100 with 2 Intel Xeon L5520 CPUs, 72GB ECC DDR3 RAM and Dual 1GB Intel NICs running Windows 8.1. I've consistently written to the Dell at a little less than 200MB/s in the past and read speeds are even faster, so I don't think the Dell is the bottleneck. The two machines are connected through an HP 2920-48G switch without LACP setup on the particular ports. However, the switch has no issue transferring at speeds much higher than 40MB/s.
After reading numerous other posts about write speed issues with CIFS shares, I've disabled Hyperthreading in the BIOS settings and have added the following Auxiliary Parameters to my CIFS service config:
ea support = no
store dos attributes = no
map archive = no
map hidden = no
map readonly = no
map system = no
I also have local master disabled and I've enabled UNIX extensions, with the server maximum protocol set for SMB3_00. Disabling Hyperthreading has seemed to help a bit with the write speed, but not much (maybe a 5-10MB/s increase - I was getting transfer speeds below 30MB/s before), but I'm still getting the same timeout issue. I do have encryption enabled on my pool along with AES-NI enabled on the CPUs in the BIOS.
Another odd, but maybe unrelated, issue is that when I disabled Hyperthreading a couple days ago I also enabled x2APIC in the CPU BIOS settings which subsequently kept causing a "kernel trap 12 with interrupts disabled" error at FreeNAS startup. As soon as I disabled x2APIC, FreeNAS booted up normally - I tested my CPU and RAM and both came back normal.
Any guidance would be greatly appreciated and thanks for all the information that is generally available through this community - it's already proven to be an invaluable resource.