Original thread here.
Hardware detailed here.
I did some more troubleshooting. Here is the summary.
I have had no issues with datasets using the default compression. It is when I make a dataset with max compression is when the problems start.
My main test data for this is a folder containing ~20 GB across 63 files. Transfer speeds are estimated averages.
I started with afp, as that is what I plan on using the most. When writing the test folder, it goes at ~100MBps, but it eventually stalls and fails.
I redid the test using sftp instead. It went at ~35 MBps and did not fail.
Doing the test with SMB went at ~65 MBps and failed, but it did take longer than to fail than AFP.
The message dump for the AFP failure is this:
Jan 20 18:23:40 freenas afpd[37036]: transmit: Request to dbd daemon (volume emc) timed out.
Jan 20 18:24:37 freenas cnid_dbd[37037]: read: Connection reset by peer
Jan 20 18:24:37 freenas cnid_dbd[37037]: error reading message header: Connection reset by peer
Jan 20 18:24:37 freenas cnid_dbd[37037]: read: Connection reset by peer
Jan 20 18:24:37 freenas cnid_dbd[37037]: error reading message header: Connection reset by peer
Jan 20 18:24:37 freenas cnid_dbd[37037]: read: Connection reset by peer
Jan 20 18:24:37 freenas cnid_dbd[37037]: error reading message header: Connection reset by peer
Jan 20 18:24:37 freenas cnid_dbd[37037]: read: Connection reset by peer
Jan 20 18:24:37 freenas cnid_dbd[37037]: error reading message header: Connection reset by peer
Jan 20 18:24:37 freenas cnid_dbd[37037]: read: Connection reset by peer
Jan 20 18:24:37 freenas cnid_dbd[37037]: error reading message header: Connection reset by peer
I looked at the log for the SMB failure but didn't notice anything other than SMB going down and coming back up again. The message in the OS X error window is this:
The Finder can’t complete the operation because some data in “2014-05-04.wav” can’t be read or written.
(Error code -36)
Another interesting observation is that when trying to delete the dataset after a failed write to it, it will fail because 'device is busy'. If I reboot or wait a while (like the time it took to write out this report), I can then delete it.
I have no idea how FreeNAS works under the hood, but I would guess that if you give it too much data too fast at high compression, it gets overloaded and crashes.
To reproduce this test, make a max compression dataset and throw a large amount of data at it as fast as you can. If you can push ~100 Mbps at it, you should see a failure in less that 20 GB!
I looked at the bug reporting page and saw that I have to register an account to 'officially' report this. I really don't want to make yet another account. I just want to be a FreeNAS user...
Hardware detailed here.
I did some more troubleshooting. Here is the summary.
I have had no issues with datasets using the default compression. It is when I make a dataset with max compression is when the problems start.
My main test data for this is a folder containing ~20 GB across 63 files. Transfer speeds are estimated averages.
I started with afp, as that is what I plan on using the most. When writing the test folder, it goes at ~100MBps, but it eventually stalls and fails.
I redid the test using sftp instead. It went at ~35 MBps and did not fail.
Doing the test with SMB went at ~65 MBps and failed, but it did take longer than to fail than AFP.
The message dump for the AFP failure is this:
Jan 20 18:23:40 freenas afpd[37036]: transmit: Request to dbd daemon (volume emc) timed out.
Jan 20 18:24:37 freenas cnid_dbd[37037]: read: Connection reset by peer
Jan 20 18:24:37 freenas cnid_dbd[37037]: error reading message header: Connection reset by peer
Jan 20 18:24:37 freenas cnid_dbd[37037]: read: Connection reset by peer
Jan 20 18:24:37 freenas cnid_dbd[37037]: error reading message header: Connection reset by peer
Jan 20 18:24:37 freenas cnid_dbd[37037]: read: Connection reset by peer
Jan 20 18:24:37 freenas cnid_dbd[37037]: error reading message header: Connection reset by peer
Jan 20 18:24:37 freenas cnid_dbd[37037]: read: Connection reset by peer
Jan 20 18:24:37 freenas cnid_dbd[37037]: error reading message header: Connection reset by peer
Jan 20 18:24:37 freenas cnid_dbd[37037]: read: Connection reset by peer
Jan 20 18:24:37 freenas cnid_dbd[37037]: error reading message header: Connection reset by peer
I looked at the log for the SMB failure but didn't notice anything other than SMB going down and coming back up again. The message in the OS X error window is this:
The Finder can’t complete the operation because some data in “2014-05-04.wav” can’t be read or written.
(Error code -36)
Another interesting observation is that when trying to delete the dataset after a failed write to it, it will fail because 'device is busy'. If I reboot or wait a while (like the time it took to write out this report), I can then delete it.
I have no idea how FreeNAS works under the hood, but I would guess that if you give it too much data too fast at high compression, it gets overloaded and crashes.
To reproduce this test, make a max compression dataset and throw a large amount of data at it as fast as you can. If you can push ~100 Mbps at it, you should see a failure in less that 20 GB!
I looked at the bug reporting page and saw that I have to register an account to 'officially' report this. I really don't want to make yet another account. I just want to be a FreeNAS user...