Hello- I recently bought new hardware and installed 11.1U4 (and even more recently updated to U5) .
Hardware is:
Core i3-6100 CPU @ 3.70GHz
16GB ram
3x 4TB drives in a mirror config
1x ssd boot drive
I'm having an issue with my Samba shares that did not exist in my FreeNAS 8.2.0. (The v8 box has not been decom yet, so I can still test against it, but it's non in use.)
On the 11.1 box, I can authenticate and access the shares. Directory list, file creation, edit, delete, all that good stuff. The problem is long time file handles break at some point with an "Invalid Signature" error on the next write. Aka:
I have an application (securecrt) running on my Win10 machine that I have configured to write log files to the Windows (SMB) share. The log files are created and written to and remain open for as long as the ssh session is open. After some undetermined period of (idle?) time, the next write to the log file causes an error to pop up saying Invalid Signature and no more logging.
According to smbstatus -v running in a loop with a 60 second delay,
the handle was still open until the write was attempted, and then disappeared from the list.
According to sysinternals procmon, secure crt still seemed to think it had an open file handle.
Most of my research regarding this error has been about the shares just not working at all. I can't find anything about "it mostly works except for long term file handles."
Secure CRT is just how I discovered this issue. I was able to create a simple script that created/opened a file on the share, and after some period of time, it also got the same error.
I'm not sure where to look next or how to address this. Seems like it would be a pretty obvious problem for people. My freenas is pretty stock, I don't have any jails or other such customizations. The machine is working great otherwise. Only other problem (annoyance, really) I have with it is that all of the "Reporting" graphs get erased on reboot, and that's pretty minor.
I also have Win7 and WinXP I can test with and cal also do some more sophisticated tests with writes to see if constant writing fails after some time, or only when there's some period of idleness after the last write.
Hardware is:
Core i3-6100 CPU @ 3.70GHz
16GB ram
3x 4TB drives in a mirror config
1x ssd boot drive
I'm having an issue with my Samba shares that did not exist in my FreeNAS 8.2.0. (The v8 box has not been decom yet, so I can still test against it, but it's non in use.)
On the 11.1 box, I can authenticate and access the shares. Directory list, file creation, edit, delete, all that good stuff. The problem is long time file handles break at some point with an "Invalid Signature" error on the next write. Aka:
Code:
NT_STATUS_INVALID_SIGNATURE 0xc000a000 The cryptographic signature is invalid.
I have an application (securecrt) running on my Win10 machine that I have configured to write log files to the Windows (SMB) share. The log files are created and written to and remain open for as long as the ssh session is open. After some undetermined period of (idle?) time, the next write to the log file causes an error to pop up saying Invalid Signature and no more logging.
According to smbstatus -v running in a loop with a 60 second delay,
Code:
83772 21109 DENY_WRITE 0x100085 RDONLY LEASE(RWH) /mnt/primary/software Internet/VanDyke/scrt/logs/20180611-bucket.log Mon Jun 11 18:25:31 2018
the handle was still open until the write was attempted, and then disappeared from the list.
According to sysinternals procmon, secure crt still seemed to think it had an open file handle.
Most of my research regarding this error has been about the shares just not working at all. I can't find anything about "it mostly works except for long term file handles."
Secure CRT is just how I discovered this issue. I was able to create a simple script that created/opened a file on the share, and after some period of time, it also got the same error.
Code:
irb(main)> fh = open('filehandle-test.txt', 'wb') => #<File:filehandle-test.txt> (note: this is a "good" response) irb(main)> fh.write("\n"+Time.now.to_s) ; fh.flush => #<File:filehandle-test.txt> irb(main)> fh.write("\n"+Time.now.to_s) ; fh.flush => #<File:filehandle-test.txt> irb(main)> fh.write("\n"+Time.now.to_s) ; fh.flush Errno::E-21468: Invalid Signature. from (irb):17:in `flush' from (irb):17 from C:/Ruby24-x64/bin/irb.cmd:19:in `<main>'
I'm not sure where to look next or how to address this. Seems like it would be a pretty obvious problem for people. My freenas is pretty stock, I don't have any jails or other such customizations. The machine is working great otherwise. Only other problem (annoyance, really) I have with it is that all of the "Reporting" graphs get erased on reboot, and that's pretty minor.
I also have Win7 and WinXP I can test with and cal also do some more sophisticated tests with writes to see if constant writing fails after some time, or only when there's some period of idleness after the last write.