I had a switch issue which caused an interruption to storage traffic. This in turn seemed to have broke a couple of Windows 2012 VMs, they have write-caching enabled.
Looking at the description surrounding the use of write-caching it says that it should only be enabled if there is a guarantee that the storage can be written to. It also mentions about blue screening or an OS issue could cause the system to reboot before the data is written to disk.
What are others doing with VMs where their disks are elsewhere? I've disabled write-caching on one of the VMs as a precaution. I didnt like the idea of a OS crash causing the system to be corrupt.
ps. it's so handy being able to instantly revert to a previous snapshot.
Nutanix. Because internal hard drives are awesome.
I've always turned off write caching, though, even on hardware back in the day. There are just too many things that can go wrong with it.
Cool, so good move for me then :)
Quote from: Dieselboy on April 07, 2017, 09:03:01 PM
Cool, so good move for me then :)
The only guys who wanted it were the database guys, because performance. Anything that promises performance, they want on. And then, when that thing they had us turn on results in a system failure, they're all
:whatudo: