0xbadfca11
commented
3 years ago Your Linux filesystem has corrupted. Do
sudo mount -o remount,ro /dev/sdb
sudo e2fsck -p /dev/sdb
wsl.exe --shutdown
Closed guillotjulien closed 3 years ago
0xbadfca11
commented
3 years ago Your Linux filesystem has corrupted. Do
sudo mount -o remount,ro /dev/sdb
sudo e2fsck -p /dev/sdb
wsl.exe --shutdown
guillotjulien
commented
3 years ago That wasn't enough to resolve the issue (same problem happen after executing the commands), however, e2fsck prompted to use fsck to resolve bad blocks, which I did, and it seems to have resolved the issue.
YmirWang
commented
5 months ago This seems to be consistent with the problem I encountered. When encountering this problem, even if it is restarted, the problem will still occur and cannot be recovered. Do you have the above solution later and how to avoid this problem from happening?
BTW：My Linux kernel version is also 4.19.275
YmirWang
commented
5 months ago run fsck, e2fsck,fsck.ext4, none of these can solve the problem. EXT4-fs error (device flash-protect-rw): ext4_validate_block_bitmap:384: comm PsmSsp: bg 0: bad block bitmap checksum EXT4-fs (flash-protect-rw): Delayed block allocation failed for inode 12 at logical offset 0 with max blocks 1 with error 74 EXT4-fs (flash-protect-rw): This should not happen!! Data will be lost
Environment
Steps to reproduce
cp /mnt/c/User/test/bigfile /another/location/homeor any other place result inRead-only file system(touch: cannot touch 'test': Read-only file system)After a
wsl --shutdown, file system is writable again, and performing the aforementionned steps create the problem again.dmesg output:
WSL logs: https://aka.ms/AAar55x
Expected behavior
Copy either work or fail without making the whole fs read only.
Actual behavior
Failed operation result in read only file system