WSL2 reapting error fills syslog and kern.log massively | pressku.com

Trending 1 month ago

I conscionable installed WSL2 to yet usage Docker connected my dev PC. Some days later I recognized that I americium moving retired of disk abstraction moreover though I americium having a 1TB disk. After checking nan logic it was caused by nan WSL2 Ubuntu distro. I uninstalled WSL2 and sewage my disk abstraction back. After reinstalling it nan aforesaid happened again. Digging deeper leads maine to /var/log which is stadily increasing. Then I saw that kern.log and syslog are occupying immense disk abstraction of approx 40GB each (after a mates of hours): ls -lh /var/log

This is nan correction which repeats successful some log files of astir 100 times per second:

sudo tail -n 100 /var/log/kern.log | less Feb 19 08:24:44 md2s67dc kernel: [ 855.493826] hv_storvsc fd1d2cbd-ce7c-535c-966b-eb5f811c95f0: tag#208 cmd 0x28 status: scsi 0x2 srb 0x4 hv 0xc0000001 Feb 19 08:24:44 md2s67dc kernel: [ 855.493995] hv_storvsc fd1d2cbd-ce7c-535c-966b-eb5f811c95f0: tag#208 cmd 0x28 status: scsi 0x2 srb 0x4 hv 0xc0000001 Feb 19 08:24:44 md2s67dc kernel: [ 855.494159] hv_storvsc fd1d2cbd-ce7c-535c-966b-eb5f811c95f0: tag#208 cmd 0x28 status: scsi 0x2 srb 0x4 hv 0xc0000001 Feb 19 08:24:44 md2s67dc kernel: [ 855.494386] hv_storvsc fd1d2cbd-ce7c-535c-966b-eb5f811c95f0: tag#208 cmd 0x28 status: scsi 0x2 srb 0x4 hv 0xc0000001 Feb 19 08:24:44 md2s67dc kernel: [ 855.494651] hv_storvsc fd1d2cbd-ce7c-535c-966b-eb5f811c95f0: tag#208 cmd 0x28 status: scsi 0x2 srb 0x4 hv 0xc0000001 Feb 19 08:24:44 md2s67dc kernel: [ 855.494884] hv_storvsc fd1d2cbd-ce7c-535c-966b-eb5f811c95f0: tag#208 cmd 0x28 status: scsi 0x2 srb 0x4 hv 0xc0000001 Feb 19 08:24:44 md2s67dc kernel: [ 855.495089] hv_storvsc fd1d2cbd-ce7c-535c-966b-eb5f811c95f0: tag#208 cmd 0x28 status: scsi 0x2 srb 0x4 hv 0xc0000001 Feb 19 08:24:44 md2s67dc kernel: [ 855.495265] hv_storvsc fd1d2cbd-ce7c-535c-966b-eb5f811c95f0: tag#208 cmd 0x28 status: scsi 0x2 srb 0x4 hv 0xc0000001 Feb 19 08:24:44 md2s67dc kernel: [ 855.495483] hv_storvsc fd1d2cbd-ce7c-535c-966b-eb5f811c95f0: tag#208 cmd 0x28 status: scsi 0x2 srb 0x4 hv 0xc0000001

This is nan wsl type that I americium running:

wsl --version WSL-Version: 2.0.9.0 Kernelversion: 5.15.133.1-1 WSLg-Version: 1.0.59 MSRDC-Version: 1.2.4677 Direct3D-Version: 1.611.1-81528511 DXCore-Version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows-Version: 10.0.19044.3930 Enterprise Edition

here are nan Ubuntu details:

cat /etc/*release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04.3 LTS" PRETTY_NAME="Ubuntu 22.04.3 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.3 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"

Currently I flooded this rumor by limiting nan size of syslog and kern.log and fto logrotate tally each hour. But I would for illustration to lick nan existent problem alternatively of relieving nan effect it has.

The correction connection is excessively cryptical for me. Does anybody knows what this correction means? Did 1 ever observe akin behaviours? How tin I extremity this error?

Any thief is highly appreciated! Thanks

More
close