Hi,
I'm running a fairly large FreeNAS installation and exporting 3 iSCSI LUNs to a Windows Server 2016. (1 LUN is exported to a Linux server via iSCSI, I don't believe this is having issues)
I am using MPIO on all LUNs, connected via 2x 10GbE
LUNs are sized as follows:
a) 45TB
b) 2TB
c) 85TB
Recently, I've been starting to get issues where Windows will not let me browse certain folders. The exact error message is:
This problem seems to come and go, if I revisit the folder at a later time it may work. For example right now as I type this, it's working fine - all LUNs and all folders are working with no issue. However a few hours ago without me touching anything, I received the I/O errors from Windows.
If I offline the disk in Disk Manager and online it again, things work fine for a while.
It's important to note that this system has worked flawlessly for over a year now at the very least, it's almost as if overnight the issues started occurring.
Additionally, I occasionally see the following errors in the Windows event log:
A ZFS Scrub comes up fine, a Windows chkdsk /R also comes up fine with no errors.
This FreeNAS system was previously running 9.10, I've upgraded it to 11.1 recently however the issue persists.
It's running on Supermicro hardware with the following:
I'm hoping someone may be able to point me in the right direction.
I have a feeling this is less FreeNAS related and more hitting Windows NTFS limits (although I did check and I'm below the maximums). I know switching to the ZFS filesystem and using FreeNAS to expose shares could probably work better in my case, but my trade off would be losing the 2x 10GbE MPIO if I did that (last I saw, SMB3 multi-channel was still experimental)
I also know of the 80% performance degradation, and the 50% capacity utilization when using iSCSI LUNs, but from my understanding that would just affect performance and not give me errors such as what I'm experiencing?
I'm running a fairly large FreeNAS installation and exporting 3 iSCSI LUNs to a Windows Server 2016. (1 LUN is exported to a Linux server via iSCSI, I don't believe this is having issues)
I am using MPIO on all LUNs, connected via 2x 10GbE
LUNs are sized as follows:
a) 45TB
b) 2TB
c) 85TB
Recently, I've been starting to get issues where Windows will not let me browse certain folders. The exact error message is:
Code:
X:\ is not accessible. The request could not be performed because of an I/O device error.
This problem seems to come and go, if I revisit the folder at a later time it may work. For example right now as I type this, it's working fine - all LUNs and all folders are working with no issue. However a few hours ago without me touching anything, I received the I/O errors from Windows.
If I offline the disk in Disk Manager and online it again, things work fine for a while.
It's important to note that this system has worked flawlessly for over a year now at the very least, it's almost as if overnight the issues started occurring.
Additionally, I occasionally see the following errors in the Windows event log:
Code:
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: X:, DeviceName: \Device\HarddiskVolumeX. (The I/O device reported an I/O error.)
Code:
Disk X has crossed a capacity utilization threshold and used Y bytes. When the threshold was crossed, the pool had Z bytes of remaining capacity.
A ZFS Scrub comes up fine, a Windows chkdsk /R also comes up fine with no errors.
This FreeNAS system was previously running 9.10, I've upgraded it to 11.1 recently however the issue persists.
It's running on Supermicro hardware with the following:
Code:
2x Xeon E5-2620 v3 128GB RAM Intel 10GbE SFP+ NICs Raw space: 282TB Used, 53TB Available (84%) 11x RAIDZ2 vdevs containing 6 drives in each (HGST HUS726060AL4210 A7J0 - 7200 SAS)
I'm hoping someone may be able to point me in the right direction.
I have a feeling this is less FreeNAS related and more hitting Windows NTFS limits (although I did check and I'm below the maximums). I know switching to the ZFS filesystem and using FreeNAS to expose shares could probably work better in my case, but my trade off would be losing the 2x 10GbE MPIO if I did that (last I saw, SMB3 multi-channel was still experimental)
I also know of the 80% performance degradation, and the 50% capacity utilization when using iSCSI LUNs, but from my understanding that would just affect performance and not give me errors such as what I'm experiencing?
