Forum Discussion
Server 2022 and Server vNext build 25931 corrupts filesystem with deduplication profile HyperV/VDI
A little update on this: I could reproduce it on a HP DL380 Gen10 with a Dual Xeon Gold 6226R, full flash and 1 TB RAM, running Server 2019 on the host.
Seems this bug only surfaces on reasonable fast machines, and shows up with a higher probability when the "Ready-To-Reproduce" package is NOT on C: . The i7-4960x seems to be the lower limit, and it does not always show up when using the Tiered-SSD-HDD storage there, but always when using SSD storage. For my Ryzen it shows up on any SSD storage except when it is on C:. For the above mentioned DL380 C: is not big enough, so it was a non-system volume there too.
Ready-To-Reproduce Package for a Server 2019 host: https://joumxyzptlk.de/tmp/microsoft/S2022-nested-2023-09-30-exported-from-S2019-host.7z
Edit: That package does not require an internet connection to reproduce, therefore no LAN is configured for that VM.
Wow, thanks for posting this!
AMD EPYC 7502P 32-Core, SSD, clean updated Win2022 LTSC, deduped 100 vhdx files with hyper-v profile - after 5 minutes files corrupted.
Tried another server with same config - same situation.
Disabled dedupe - everything great.
😞
- Fir thank you for reporting / confirming!
If you can, or have the time: Try with Server 2019. No dedupe problem there, at least none I stumbled upon. Or try a slower CPU :D.
