Forum Discussion

Joachim_Otahal's avatar
Joachim_Otahal
Iron Contributor
Feb 26, 2024

26063 deduplication data corruption is still there.

From Server 2022 up to this newest 26063 build, they all have the same problem, as described here: https://techcommunity.microsoft.com/t5/windows-server-insiders/server-vnext-26040-and-server-2022-de...
Hyper-V
storage
MSBernstein's avatar
MSBernstein
Icon for Microsoft rankMicrosoft
Feb 27, 2024
Hi, Joachim. Sorry you are feeling frustrated about this -- we do have a lot of different demands on our time in any given day; we are as human as you are. I work in engineering, not marketing. I'm trying to see if the de-dup team has enough data to diagnose this, given the feedback you've provided.

Thanks,
Michael Bernstein (MSFT)
Joachim_Otahal's avatar
Joachim_Otahal
Iron Contributor
Feb 29, 2024
If you want to look how it plays out with Server 2022 and nVext: I recorded a video which is on my home page https://www.joumxyzptlk.de/tmp/microsoft/S2022-Nested_Deduplication_VDI-Hyperv_profile_kills_filesystem_v2.mp4
Video was created on AMD Ryzen 5950 with Win11 as host, but is the same on Dual Xeon 6226R with Server 2019 (HP ProLiant DL380) as host.
  • MSBernstein's avatar
    MSBernstein
    Icon for Microsoft rankMicrosoft
    Feb 29, 2024
    Thanks, Joachim! I attached that video to the bug report to provide additional context for the engineering team.
    • Joachim_Otahal's avatar
      Joachim_Otahal
      Iron Contributor
      Mar 07, 2024
      Could the engineering reproduce this bug, maybe even as easy as I can? I don't expect a fix so fast, but if they could reproduce it would be a good feedback.
      • MSBernstein's avatar
        MSBernstein
        Icon for Microsoft rankMicrosoft
        Mar 08, 2024
        I checked on the bug report. As far as I can tell, the engineering team is still working to reproduce the issue.
    • Joachim_Otahal's avatar
      Joachim_Otahal
      Iron Contributor
      Feb 29, 2024

      Thank you for your Update! This is great. Update from my side:
      I've retested with ReFS on 26063 today: Could not reproduce deduplication corruption with ReFS. Tested with all three profiles today, "HyperV" (aka VDI in GUI), "Default" (aka Fileserver in GUI) and "Backup". It seems to be limited to NTFS-Deduplication where I could re-reproduce after those tests exactly the same way as usual.
      If your engineering team is interested in "ready to reproduce packages, Version 26063, exported from Server 2019 host" just say. IMHO the existing packages with Server 2022 and Server 26040 should be enough, but if they need it I'll do it. Same goes for retesting Server 2022 + ReFS which I skip today since it is 22:37 local time.
      If you look at this thread I started last September: Someone else had a similar problem with Server 2022 https://techcommunity.microsoft.com/t5/windows-server-for-it-pro/server-2022-and-server-vnext-build-25931-corrupts-filesystem/m-p/3915647
      Additional Information: I've been in contact with Philipp Kuhn (Philipp.Kuhn insert at character here microsoft dot character com), but he has no access to resources to reproduce this. His private machines don't have enough RAM and he really tried, and with Azure Test VMs he provided we could not reproduce since double nested virtualization does not work there.

Resources