Anthony Chastain
Dabbler
- Joined
- Jul 27, 2017
- Messages
- 16
I am new to the forum, but I've been using FreeNAS for about a year.
I am running FreeNAS-11.0-U2 (e417d8aa5) on ESXi (with direct disk access, of course), with RAIDZ2 on 7 x 4TB hard drives with 28 GB of memory with Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz (x8). As of now, we're storing about 13 TiB.
We have a lot going on: filming, photography and editing, document sharing, software development, and video encoding. In addition to this, we have backups being made daily to s3 using s3cmd (which also does checksums on the new data). Most of our clients are Windows 10, and a few are apple, but use SMB anyway to keep consistent relative path names.
For the past two weeks, the SMB service has randomly been crashing, sometimes only minutes after re-enabling it. When it crashes, I have to manually turn the service back on from the UI.
I've set the logs to debug and see things like
It seems to happen only when it's under a heavy load and only in the last two weeks. So my question is, where do I even start trying to figure out what is causing this problem? Do I submit a bug or is there a setting that I'm missing?
I am running FreeNAS-11.0-U2 (e417d8aa5) on ESXi (with direct disk access, of course), with RAIDZ2 on 7 x 4TB hard drives with 28 GB of memory with Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz (x8). As of now, we're storing about 13 TiB.
We have a lot going on: filming, photography and editing, document sharing, software development, and video encoding. In addition to this, we have backups being made daily to s3 using s3cmd (which also does checksums on the new data). Most of our clients are Windows 10, and a few are apple, but use SMB anyway to keep consistent relative path names.
For the past two weeks, the SMB service has randomly been crashing, sometimes only minutes after re-enabling it. When it crashes, I have to manually turn the service back on from the UI.
I've set the logs to debug and see things like
PANIC (pid 5720): invalid lock_order
and smb_panic(): action returned status 0
I would include it, but 3 seconds worth is about 40 MB.It seems to happen only when it's under a heavy load and only in the last two weeks. So my question is, where do I even start trying to figure out what is causing this problem? Do I submit a bug or is there a setting that I'm missing?