Mounted drive is accessible locally, but not accessible when using a remote (ssh) session.

[rikrdo89]

A RAID device /dev/md0 is successfully mounted locally at /mnt/raid, however, it is not visible when accessing it using a remote session (via SSH, same user). Similarly, I when mounting the device during a remote (ssh) session, the mount is not visible when trying to access it locally. The mount seems to only be visible and accessible within the same session (remote or local), but not across them.

Windows Version

Microsoft Windows [Version 10.0.22631.4602]

WSL Version

2.3.26.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.167.4-1

Distro Version

Ubuntu 22.04

Other Software

No response

Repro Steps

Create a Mount Point:

sudo mkdir -p /mnt/raid

Mount the drive in local session:

sudo mount /dev/md0 /mnt/raid

Verify the mount

mount | grep /mnt/wsl/raid
/dev/md0 /mnt/raid ext4 rw,relatime,stripe=256 0 0

Accessing the machine remotely via ssh does not show the mounted drive.
mount | grep /mnt/wsl/raid does not show anything,

Expected Behavior

lsblk in both local and remote session should show (screenshot from local session):

Actual Behavior

lsblk in remote session does not show the array as mounted:

Diagnostic Logs

No response

[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 , SSH and windows mounts (#8405), similarity score: 0.78
• sshfs contents only visible in Windows Explorer when mounted in /mnt/wsl and /mnt/wslg (#8423), similarity score: 0.73
• Explorer unable to access SSHFS mounted directory (#8498), similarity score: 0.71
• Unable to see mounted files via explorer.exe (#7834), similarity score: 0.70

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

[craigloewen-msft]

Can you make sure this is mounted in /mnt/wsl/raid instead of /mnt/raid

The reasoning behind this is that when accessing WSL from a remote connection you are running in a different context which might behave slightly differently for scenarios like this.

[rikrdo89]

Thanks, using /mnt/wsl/raid instead of /mnt/ as my mounting directory works.

However, I still don't fully understand why this would not work even if the mounting point is a directory under $HOME. I guess I failed to see if the different context when logging remotely via SSH is a feature or a bug.