WSL2 reapting error fills syslog and kern.log massively

I just installed WSL2 to finally use Docker on my dev PC. Some days later I recognized that I am running out of disk space even though I am having a 1TB disk. After checking the reason it was caused by the WSL2 Ubuntu distro. I uninstalled WSL2 and got my disk space back. After reinstalling it the same happened again. Digging deeper leads me to /var/log which is stadily increasing. Then I saw that kern.log and syslog are occupying huge disk space of approx 40GB each (after a couple of hours): ls -lh /var/log

This is the error which repeats in both log files of about hundred times per second:

sudo tail -n 100 /var/log/kern.log | lessFeb 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 0xc0000001Feb 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 0xc0000001Feb 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 0xc0000001Feb 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 0xc0000001Feb 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 0xc0000001Feb 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 0xc0000001Feb 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 0xc0000001Feb 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 0xc0000001Feb 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 the wsl version that I am running:

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

here are the Ubuntu details:

cat /etc/*releaseDISTRIB_ID=UbuntuDISTRIB_RELEASE=22.04DISTRIB_CODENAME=jammyDISTRIB_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=jammyID=ubuntuID_LIKE=debianHOME_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"

I already tried to check the filesystem but it fails:

sudo e2fsck /dev/sdc -p/dev/sdc is mounted.e2fsck: Cannot continue, aborting.

Instead I used fsck which seems to be fine.

fsck -nf /dev/sdcfsck from util-linux 2.37.2e2fsck 1.46.5 (30-Dec-2021)Warning!  /dev/sdc is mounted.Warning: skipping journal recovery because doing a read-only filesystem check.Pass 1: Checking inodes, blocks, and sizesPass 2: Checking directory structurePass 3: Checking directory connectivityPass 4: Checking reference countsPass 5: Checking group summary informationFree blocks count wrong (263925079, counted=263925061).Fix? noFree inodes count wrong (67108093, counted=67108070).Fix? no/dev/sdc: 771/67108864 files (0.1% non-contiguous), 4510377/268435456 blocks

Currently I overcome this issue by limiting the size of syslog and kern.log and let logrotate run every hour. But I would like to solve the actual problem instead of relieving the effect it has.

I also checked my other computers where WSL2 is running for months already. And I am discovering the same error message. Obviously the config of logrotate was already appropriated enough that I didnt recognize this error so far.

The error message is too cryptical for me. Does anybody knows what this error means? Did one ever discover similar behaviours? How can I stop this error?

Any help is highly appreciated! Thanks