From reading on troubleshooting and a long support call the Storage Spaces Drt counters for a storage spaces direct volume are never supposed to be greater than the limit. If the limit is breached then the volume is supposed to stay offline. I have noticed that some volumes go offline when I reboot a cluster node after putting it into maintenance in failover cluster manager. I haven't yet had an opportunity to try it yet, but there are a few commands to run.
Get-StorageFaultDomain -type StorageScaleUnit | Where-Object {$_.FriendlyName -eq "cl-hv03"} | Enable-StorageMaintenanceModehttps://social.technet.microsoft.com/Forums/en-US/4fc1fb86-61fa-4976-8b3f-9e314586fef8/storage-spaces-direct-cluster-virtual-disk-goes-offline-when-rebooting-a-node?forum=winserverClustering
I have KB4462928 installed on all the cluster nodes as well.
Where this really gets interesting is that I have a volume that is online with a dirty count greater than the limit, and I'm not sure how this is possible and if there is a way to clear the DRT backlog. Even when nothing is writing to the volume, it stays above 270 when the limit is 255.
I'd post links and screen shots but my account hasn't been verified yet.
