Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
1 of 2 tasks
rikrdo89 opened this issue Jan 9, 2025 · 1 comment
Open
1 of 2 tasks

Comments

@rikrdo89
Copy link

rikrdo89 commented Jan 9, 2025

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):

Image

Actual Behavior

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

Image

Diagnostic Logs

No response

Copy link

github-actions bot commented Jan 9, 2025

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:

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant