- Joined
- Feb 2, 2018
- Messages
- 1,401
Hi,
First server (Dell T-110 ; 8Gig RAM ECC ; Intel CPU i3-2100 CPU @ 3.10GHz ; 5x IronWolf 3TB RaidZ-2) is doing fine with FreeNAS 11.2-rc2.
Second server (Dell T-130 ; 16Gig RAM ECC ; Intel Xeon E1230-v6 3.5GHz ; 5x IronWolf 4TB RaidZ-2), not so much.
After a lot of problems with the USB boot, I changed the USB key and installed 2 of them as mirror because it was detaching all the time within max 2 days.
After few days without problems on USB, I started to move my data out of Server 2 back to Server 1 for me to rebuild the pool. When trying to empty he iSCSI datastore, transfer started in the 400 mbps as expected, but dropped to about 20. On the console, I found a million lines of swap errors. Because the second server is still new, I re-started a second set of memtest to see if the RAM is wrong. Still no error after some more complete memtest runs. I have no jail, no plugins, no SMB, no AFP, only NFS, iSCSI and zfs replication tasks running. About that replication, the full sync was over ago and only very minimalistic daily changes were to be propagated.
Server1 did not suffered any problem at all, with the same data, sending / receiving the same data, offering the same NFS shares, over the same network and all, BUT for the iSCSI. iSCSI is the only thing that I never configured on Server1.
Considering how memory problems often translate in random and strange seemingly unrelated malfunctions, I suspect there may be a memory leak or something like that in iSCSI in v11.2-rc2. Unfortunately, I have to build that server, configure it, deploy the data and stage it for long enough before sending it offsite. As such, I can not keep investigating the incident.
iSCSI client was ESXi 6.7 U1, latest build and patches. Connection was direct (no switch) from server's built-in broadcom NIC and extra PCIe Intel NIC (2 cables) and configured to distribute IO over the 2 links equally (max IOP=1).
Should you need more input about how I was configured, it will be my pleasure to tell you more.
Sorry not to have time to investigate beyond that....
Heracles31
First server (Dell T-110 ; 8Gig RAM ECC ; Intel CPU i3-2100 CPU @ 3.10GHz ; 5x IronWolf 3TB RaidZ-2) is doing fine with FreeNAS 11.2-rc2.
Second server (Dell T-130 ; 16Gig RAM ECC ; Intel Xeon E1230-v6 3.5GHz ; 5x IronWolf 4TB RaidZ-2), not so much.
After a lot of problems with the USB boot, I changed the USB key and installed 2 of them as mirror because it was detaching all the time within max 2 days.
After few days without problems on USB, I started to move my data out of Server 2 back to Server 1 for me to rebuild the pool. When trying to empty he iSCSI datastore, transfer started in the 400 mbps as expected, but dropped to about 20. On the console, I found a million lines of swap errors. Because the second server is still new, I re-started a second set of memtest to see if the RAM is wrong. Still no error after some more complete memtest runs. I have no jail, no plugins, no SMB, no AFP, only NFS, iSCSI and zfs replication tasks running. About that replication, the full sync was over ago and only very minimalistic daily changes were to be propagated.
Server1 did not suffered any problem at all, with the same data, sending / receiving the same data, offering the same NFS shares, over the same network and all, BUT for the iSCSI. iSCSI is the only thing that I never configured on Server1.
Considering how memory problems often translate in random and strange seemingly unrelated malfunctions, I suspect there may be a memory leak or something like that in iSCSI in v11.2-rc2. Unfortunately, I have to build that server, configure it, deploy the data and stage it for long enough before sending it offsite. As such, I can not keep investigating the incident.
iSCSI client was ESXi 6.7 U1, latest build and patches. Connection was direct (no switch) from server's built-in broadcom NIC and extra PCIe Intel NIC (2 cables) and configured to distribute IO over the 2 links equally (max IOP=1).
Should you need more input about how I was configured, it will be my pleasure to tell you more.
Sorry not to have time to investigate beyond that....
Heracles31