Forum Discussion

  • Build 26080 : Still as easy to reproduce as ever since Server 2022. Without deduplication those VMs update just fine without blue screen and other weirdness.

    If there is interest I'll create an 26080 export of the repo from a Server 2019 machine (which should import in Server 2019, Server 2022 and Windows 11 without problems).

     

    • MSBernstein's avatar
      MSBernstein
      Icon for Microsoft rankMicrosoft
      Thanks, Joachim. I updated the bug report to note that 26080 is included.

      Michael

      • Joachim_Otahal's avatar
        Joachim_Otahal
        Iron Contributor

        A little update on this: For the first time in many years I had a blue screen on my actual server, which was Server 2019 until mid last year. The first one ever. Bluescreenview from nirsoft lists "ntfs.sys" as culpruit. I unprofessionaly suspect concurrent writes on the deduped volume residing on a tiered mirrored storage space (not S2D). And I unprofessionally suspect that it might be related to the issue with the dedup repo which corrupts data. But only you can tell, not me.

        Computer:
        i7-4960x, 32 GB RAM (ASRock x79 Fataility). Powersupply a Fujitsu 750 Watt Ex-Primergy.
        C: = normal SSD,
        😧= Deduped drive. Tiered Storage Space Mirror, 2*SSD, 2*HDD.
        E: = Storage Spaces Parity with four drives.
        Bitlocker aktive on 😧 and E:

        Using NetQoS the speed is limited to 60 MB/s incoming since the tiered storage space cannot write faster. The blue screen happened during three parallel robocopy jobs over network, two of them with 😧 as destination. When the blue screen happened neither a dedupjob, nor a re-tiering job was running according to the event logs. After the crash and the filesystem check I copied linear, not concurrently, on and everything seemed fine.
        This is the first ntfs.sys crash I saw anyway since about, maybe, XP SP0?
        Here is the dump + the events around that crash.
        https://joumxyzptlk.de/tmp/microsoft/NTFS-maybe-dedup-problem-first-server-2022-crash-ever-on-that-computer.7z

         

  • 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)

Resources