Environment
Windows build number: Microsoft Windows [Version 10.0.21337.1010]
Your Distribution version: Release: 10
Whether the issue is on WSL 2 and/or WSL 1: Linux version 5.4.91-microsoft-standard-WSL2 (oe-user@oe-host) (gcc version 9.3.0 (GCC)) #1 SMP Mon Jan 25 18:39:31 UTC 2021
Steps to reproduce
- give wsl a disk
wsl --mount \\.\PHYSICALDRIVE1 --bare
- format it in btrfs
sudo mkfs.btrfs /dev/sdc
- mount the filesystem
sudo mount -o ssd,noatime,space_cache,commit=120,compress /dev/sdc /mnt/test
- optional, be incredibly liberal with permissions
chown $USERNAME:$USERNAME /mnt/test; chmod ugo+rwx /mnt/test
- attempt to open
\\wsl$\Debian\mnt\test in explorer
WSL logs: wsl.etl.log
Expected behavior
Windows has access to the btrfs drive.
Actual behavior

"is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.
Attempt to access invalid address."
The exact same issue was reported on the original blogpost about --mount but the fix is sshfs-specific
Environment
Steps to reproduce
wsl --mount \\.\PHYSICALDRIVE1 --baresudo mkfs.btrfs /dev/sdcsudo mount -o ssd,noatime,space_cache,commit=120,compress /dev/sdc /mnt/testchown $USERNAME:$USERNAME /mnt/test; chmod ugo+rwx /mnt/test\\wsl$\Debian\mnt\testin explorerWSL logs: wsl.etl.log
Expected behavior
Windows has access to the btrfs drive.
Actual behavior
"is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.
Attempt to access invalid address."
The exact same issue was reported on the original blogpost about
--mountbut the fix issshfs-specific