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

Unable to use luks mounted filesystem #12150

Closed
1 of 2 tasks
grobx opened this issue Oct 10, 2024 · 2 comments
Closed
1 of 2 tasks

Unable to use luks mounted filesystem #12150

grobx opened this issue Oct 10, 2024 · 2 comments

Comments

@grobx
Copy link

grobx commented Oct 10, 2024

Windows Version

Microsoft Windows [Version 10.0.22631.4169]

WSL Version

2.3.24.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

Linux version 5.15.153.1-microsoft-standard-WSL2 (root@941d701f84f1) (gcc (GCC) 11.2.0, GNU ld (GNU Binutils) 2.37) #1 SMP Fri Mar 29 23:14:13 UTC 2024

Distro Version

Ubuntu 22.04

Other Software

No response

Repro Steps

Inside Ubuntu:

sudo -s
cd
apt update
apt install cryptsetup-bin
dd if=/dev/urandom of=disk.dd bs=4k count=100000
loop=$(losetup --find --show disk.dd)
cryptsetup luksFormat $loop
cryptsetup open $loop loop
mkfs.ext4 /dev/mapper/loop
mkdir /mnt/loop
mount /dev/mapper/loop /mnt/loop
touch /mnt/loop/some.file

From Windows:

  • Open /mnt/loop in Ubuntu using Explorer
  • Create a file (New > Text Document) and put something in it

Expected Behavior

  • I expect some.file to be shown in Explorer
  • I expect the Text Document created from Windows to be in the drive mounted in /mnt/loop (/root/disk.dd in this case) not in the directory /mnt/loop

Actual Behavior

  • The file some.file is not there
  • The new Text Document is created in the directory /mnt/loop instead of the mounted drive in /mnt/loop (you can confirm this by unmounting /mnt/loop)

Diagnostic Logs

No response

Copy link

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 wsl-gh-logs@microsoft.com 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!

Open similar issues:

Closed similar issues:

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

@grobx
Copy link
Author

grobx commented Oct 11, 2024

It works now, closing this.

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

No branches or pull requests

1 participant