@stephc_msft -
First, I want to thank you for all the continued effort to support fixing this problem. I'm sure everyone here agrees that you've done an amazing job triaging and relaying info between customers and PG. Truly appreciated.
Before I commit to "testing" WS2025 for you, I need some basic info:
First, I want to thank you for all the continued effort to support fixing this problem. I'm sure everyone here agrees that you've done an amazing job triaging and relaying info between customers and PG. Truly appreciated.
Before I commit to "testing" WS2025 for you, I need some basic info:
- Do we have any info on how what conditions are required to trigger the repro? (VHDX size? Average IO size? RAM in system?) In other words, what does the Hyper-V and backup scenario need to be to get this to happen?
- When would VHDX IO with host ever NOT be unbuffered? - this was surprisng to read. I assumed all VHDX IO was by default unbuffered. What is causing it to be buffered instead? Is this because the RO handle to the VHDX during backup has to pass thru a 3rd party filter/driver? Is it because you can instruct VHDMP how you want the VHDX opened (buff vs unbuff)? Like... what is causing the buffered IO to occur and where in the filter stack is that happening?
Statistics: Posted by eponerine — Jul 16, 2024 11:59 am
