Corrupted WSL2 after large files delete

[Alexsimulation]

Windows Version

10.0.22621 Build 22621

WSL Version

2.0.9.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.133.1-1

Distro Version

Ubuntu-18.04

Other Software

No response

Repro Steps

• write about 100gb of data to files under a subdir of my home wsl ubuntu directory.
• remove all the files using rm -rf
• blue screen crash
• after that, launching wsl yields the following errors:

Failed to attach disk 'C:\Users\myuser\AppData\Local\Packages\CanonicalGroupLimited.Ubuntu18.04onWindows_79rhkp1fndgsc\LocalState\ext4.vhdx' to WSL2: The file or directory is corrupted and unreadable.
Error code: Wsl/Service/CreateInstance/MountVhd/HCS/0x80070570

Expected Behavior

wsl.exe opening correctly

Actual Behavior

wsl.exe fails to launch with error print given above.

Diagnostic Logs

No response

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

• WSL2 reliably crashes when handling files > 10GB (#5410), similarity score: 0.80

Closed similar issues:

• WSL filesystem keeps accumulating corrupted file and directory entries (#1662), similarity score: 0.81
• WSL2 (Ubuntu) has partially deleted itself twice (#8876), similarity score: 0.80
• Corrupted WSL (#7016), similarity score: 0.80
• WSL got corrupted (#3536), similarity score: 0.79

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[OneBlue]

Unfortunately this is a symptom of NTFS corruption. Might be caused by your physical disk being in a bad state. You can try to run chkdsk /f but most likely the distro needs to be reinstalled.