WSL2-Kernel: enable F2FS filesystem support as a module
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 33.7k
- Forks
- 1.8k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 116
Description
**Is your feature request related to a problem? Please describe.**
Hi, everybody. I'm an Android custom ROMs developer and often use WSL2 environment when making small changes directly to system images. Because some of my devices use F2FS as their system filesystem I cannot mount and edit them on a WSL2 environment.
**Describe the solution you'd like**
Please enable support for mounting and editing F2FS filesystems in the WSL2 environment. I understand that some people may not want it by default for some reason but because it can be built as a module gives the end user even more choice and flexibility.
**Describe alternatives you've considered**
I have considered using native Linux environments or alternative filesystems, but these options are less convenient and efficient. Until now, I've been building the WSL2 Linux kernel every time with F2FS configuration enabled.
**Additional context**
I have already made this patch which should easily solve this issue. https://github.com/Fede2782/WSL2-Linux-Kernel/commit/d8c6a83db0dc19249ee7990c578df2f3ddc6ac6c
This fixes:
```
mount: /mnt: unknown filesystem type 'f2fs'.
dmesg(1) may have more information after failed mount system call.
```
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked F2FS configuration patch and the WSL2 Linux kernel build configuration. Verify the resulting kernel exposes F2FS as a module, then confirm that an F2FS filesystem can be mounted and edited in WSL2 without the reported unknown-filesystem error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100