Bug 2223078 - enable bcachefs in kernel when it lands
Summary: enable bcachefs in kernel when it lands
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-15 09:03 UTC by Ganapathi Kamath
Modified: 2023-07-15 09:09 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ganapathi Kamath 2023-07-15 09:03:47 UTC
1. Please describe the problem:

Anticipatory bug:  
Purpose of this bug is to track landing of new filesystem bcachefs feature in fedora kernel
The bcachefs feature is close to being upstreamed.
Initially, it is going to be marked as experimental

Additional decisions:
- will it be in-kernel or as a modprobe module. Hopefully in-kernel? as this will allow bootloader-providers (grub2 etc) to try experiment as a first step towards making a bootable rootfs

One will also need a bcachefs-tools package in order to do mkfs/fsck and other fs-maintenance operations. 

REF
- https://www.phoronix.com/news/Bcachefs-Plans-For-Linux-6.6


2. What is the Version-Release number of the kernel:
NA

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :
NA

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
NA

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:

NA

6. Are you running any modules that not shipped with directly Fedora's kernel?:
NA

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.
NA


Note You need to log in before you can comment on or make changes to this bug.