Corrupted filesystem with 2.3.26

[mihaibudiu]

Windows Version

Microsoft Windows [Version 10.0.22631.4317]

WSL Version

2.3.26.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.153.1-microsoft-standard-WSL2

Distro Version

Ubuntu 22.04

Other Software

No response

Repro Steps

$ wsl --upgrade
$ bash
$ cd
$ touch x
read-only filesystem
$ sudo e2fsck /dev/sdc -y
... lost of unpleasant errors ...

Expected Behavior

Root filesystem is read-write

Actual Behavior

Could not use system

Downgrading to wsl 2.3.24.0 solved the problem after another fsck.

Diagnostic Logs

Did not save diagnostic logs, since filesystem was read-only

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

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!

Closed similar issues:

• WSL2: Read-only file system error (#6220), similarity score: 0.73
• Corrupted WSL2 after large files delete (#11179), similarity score: 0.72
• WSL runs out of space and breaks the system (#10194), similarity score: 0.71
• WSL2: The file or directory is corrupted and unreadable (#12067), similarity score: 0.71
• WSL2 File System Goes Into Read Only Mode Without Warning (#8340), similarity score: 0.71

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