I created a parity storage space on 3x external USB 4tb HDD attached to a Windows 10 1809 machine. I then moved those HDDs to a Server 2019 1809 machine and added 1x additional 4tb HDD.
I noticed there is an existing 32mb write-back cache in this HDD-only single-tier parity storage space.
Is there a way to determine where this is located or why it exists? I'm unsure if it existed on W10 machine, never checked, but imagine it must've. Only noticed it on Server 2019 machine because Server Manager displays it in the Storage Pools information.
Does Storage Spaces attempt to use host device SSDs/RAM for WBC even if they are not part of the pool? Why? Both W10 and Server 2019 machines have SSD host OS drives.