CONFIG_F2FS_FS_COMPRESSION is not set

Open
#4,165 1 comment 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
c, linux

Research direction

Start by locating the Raspberry Pi kernel configuration definitions for CONFIG_F2FS_FS_COMPRESSION and compare the settings used for the different Raspberry Pi variants. Enable the requested feature in the relevant configurations, then verify the resulting kernel configuration through /proc/config.gz and confirm that the option is no longer reported as not set.

Written by the indexing model from the issue text.

Description

Since kernel 5.6 F2FS has a transparent compression feature.
Unfortunatly even if the filesystem has been created correctly the kernel currently shipped with Raspbian/Buster it cannot be used.
As F2FS is statically compiled into the kernel and it can thus be used as root filesystem.
It would be nice to have a filesystem at hand that is a bit better suited for flash media like MMC cards. Compression does help here, too.
Please enable the feature in future kernels.

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name               Version      Architecture Description
+++-==================-============-============-=================================
ii  raspberrypi-kernel 1.20210201-1 armhf        Raspberry Pi bootloader
# uname -a
Linux knigge 5.10.11+ #1399 Thu Jan 28 12:02:28 GMT 2021 armv6l GNU/Linux

# modprobe configs
# zgrep CONFIG_F2FS_FS_COMPRESSION  /proc/config.gz
# CONFIG_F2FS_FS_COMPRESSION is not set

The same applies to kernels for other Raspberry Pi variants.

Dominant language
C
Stars
13.2k
Forks
5.5k
Avg merge
2d 21h
Merged PRs (30d)
21

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from raspberrypi/linux

All issues in raspberrypi/linux

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.