diskdiddler
Wizard
- Joined
- Jul 9, 2014
- Messages
- 2,377
I am attempting to diagnose some very intermittent and frustrating issues on my new system.
I have mirror 480GB SSD pool, 8 cores, 32GB ECC, the memory has been memtested, the system hasn't crashed once.
If I click on a share on this drive, most of the time, it's fine, opens very snappy.
Sometimes when I click it, Windows 10 does the spinning circle. We're talking in excess of 15 seconds, sometimes 30. This is *not* a share with thousands of files(!) It has been responsive earlier in the day.
I have had my system drop to sub 300KB/s writes,......... (6x8TB WD)
As soon as I stopped the DockerVM which is hosting my guacamole install, it fixed things.
Furthermore, when I start my docker VM I'm prompted with this.
"Overcommit memory?"
I have 32GB memory, docker VM set to only 3.5GB. I've seen this message so often, I can't recall if it's a normal message when you start a VM or mine is busted somehow.
On top of this, I have a robocopy log, clearly showing my system successfully copying hundreds of GB of data and then suddenly just breaking and SMB being unable to talk to the target (the new server)
Is anyone seeing anything remotely similar?
I have mirror 480GB SSD pool, 8 cores, 32GB ECC, the memory has been memtested, the system hasn't crashed once.
If I click on a share on this drive, most of the time, it's fine, opens very snappy.
Sometimes when I click it, Windows 10 does the spinning circle. We're talking in excess of 15 seconds, sometimes 30. This is *not* a share with thousands of files(!) It has been responsive earlier in the day.
I have had my system drop to sub 300KB/s writes,......... (6x8TB WD)
As soon as I stopped the DockerVM which is hosting my guacamole install, it fixed things.
Furthermore, when I start my docker VM I'm prompted with this.
"Overcommit memory?"
Code:
Memory overcommitment allows multiple VMs to be launched when there is not enough free memory for configured RAM of all VMs. Use with caution.
I have 32GB memory, docker VM set to only 3.5GB. I've seen this message so often, I can't recall if it's a normal message when you start a VM or mine is busted somehow.
On top of this, I have a robocopy log, clearly showing my system successfully copying hundreds of GB of data and then suddenly just breaking and SMB being unable to talk to the target (the new server)
Is anyone seeing anything remotely similar?