Linux File Systems for Windows and Windows Subsystem Linux (WSL)

I'm trialling Linux File Systems for Windows to have read/write access to an ext4 partition which contains a Ubuntu installation; this works as expected. In the last few Windows releases, Microsoft have introduced Windows Subsystem Linux (WSL), a way to run Linux in Windows, this is particularly useful for developers. However, it does not support various kernel features and it's not possible to mount drives directly into a WSL session. It's also not possible to mount a Linux File Systems for Windows drive in WSL.

My feature suggestion is to make the necessary changes that will allow such a drive to be mounted in WSL and additionally (if Microsoft expose an API for this) to manage the linux file system attributes and owner/group correctly.

It's possible to mount mapped network drives in WSL, e.g.

Code:

---

sudo mount -t drvfs -o rw,noatime,uid=1000,gid=1000,umask=2,fmask=113,metadata Z: /z

---

, this would be useful for part #1.

Any update on this? The Windows Subsystem for Linux is now a live non-development feature. You can install multiple Linux distributions and access them as needed.

On my machine, I have mounted my dual-boot partition as E: on windows. Under Linux (Ubuntu 18.04.1) I see C: (ntfs) as /mnt/c and D: (ntfs) as /mnt/d and I see a /mnt/e mount point, but nothing mounted there. Trying to manually mount it also fails.

$ echo dir e: | cmd.exe
Microsoft Windows [Version 10.0.17134.590]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>dir e:
Volume in drive E is ROOT
Volume Serial Number is 3ECB-DD3F

Directory of E:\

02/18/2014 04:15 PM <DIR> lost+found
03/07/2019 02:40 PM <DIR> bin
03/07/2019 02:42 PM <DIR> boot
02/18/2014 04:14 PM <DIR> cdrom
02/18/2014 04:21 PM <DIR> dev
03/12/2019 06:04 PM <DIR> etc
01/03/2015 11:17 AM <DIR> home
08/21/2018 09:40 AM <DIR> lib
08/17/2018 11:40 AM <DIR> lib64
02/18/2014 04:15 PM <DIR> media
03/12/2019 06:04 PM <DIR> mnt
05/11/2015 02:14 PM <DIR> octo
02/13/2019 04:25 PM <DIR> opt
02/18/2014 04:20 PM <DIR> proc
02/28/2019 10:25 PM <DIR> root
07/26/2017 12:37 PM <DIR> run
03/07/2019 02:41 PM <DIR> sbin
02/18/2014 04:20 PM <DIR> srv
02/18/2014 04:20 PM <DIR> sys
03/13/2019 05:30 PM <DIR> tmp
08/17/2018 01:37 PM <DIR> usr
09/07/2018 11:37 AM <DIR> var
10/30/2018 10:14 AM 1,101,824 core
06/27/2016 01:51 PM <DIR> build
10/12/2017 05:17 PM <DIR> System Volume Information
1 File(s) 1,101,824 bytes
24 Dir(s) 62,043,877,376 bytes free

C:\WINDOWS\system32>$
$ sudo mount -t drvfs E: /mnt/e
mount: /mnt/e: wrong fs type, bad option, bad superblock on E:, missing codepage or helper program, or other error.
$ cat /proc/version
Linux version 4.4.0-17134-Microsoft (Microsoft@Microsoft.com) (gcc version 5.4.0 (GCC) ) #523-Microsoft Mon Dec 31 17:49:00 PST 2018
$

Unfortunately, I face the same problem:

Quote:

---

root@laptop:/mnt# mount -t drvfs e: /mnt/e/
mount: /mnt/e: wrong fs type, bad option, bad superblock on e:, missing codepage or helper program, or other error.
<3>init: (773) ERROR: UtilCreateProcessAndWait:360: /bin/mount failed with status 0x2000

---

I found a workaround by using Cygwin instead of WSL for this purpose :) Of course not the best solution in terms of solving the technical issues but for the time being, it is okay till paragon solves the conflict between WSL and LFS for Windows.

Hey! It's been a long time! Any news on how to fix this problem?