Patch for Linux 6.15's BTRFS regression available

The Garuda Linux team has issued kernel update linux and linux-zen version 6.15.9.arch1-1.1 and 6.15.9.zen1-1.1 to address a regression potentially resulting in an unbootable system/potential data loss.

These kernel updates will be prioritized over the Arch Linux official packages automatically during the next system update. We highly recommend updating to the latest packages as soon as possible:

garuda-update
# Do not forget to reboot afterwards!

To the extent of my personal knowledge, I do not believe the linux-lts kernel is affected at this time. If you are using a third party kernel on version 6.15 or higher, we strongly recommend using linux, linux-zen or linux-lts for now (until you are sure it is patched).

To see a summary of the issue, please click here

In short, unexpected power outages or other unexpected system shutdowns can lead to an unbootable system due to an error in the BTRFS “replay” system.

The replay system is a sort of “log” of every change made to the BTRFS file system between 30 second “transaction” intervals. When you create, edit or delete a file, that will be logged in the replay log.

Here’s why we need to update the kernels:
For the sake of keeping it short, this log could become “corrupted”, or rather, the log is correct, but the kernel can’t read it anymore. Let’s say… randomly. It’s not random, but you can’t predict it, therefore, it’s random!

This makes the system unbootable. BUT, the most common way this issue is fixed is by deleting the BTRFS log. For all intents and purposes, this means potentially losing up to 30 seconds of file system changes. It’s of course unlikely any of your important files will be affected by this, but in our opinion, any preventable data loss is too much data loss. Needless to say, the inconvenience of your system failing to boot or potentially missing a job interview because you couldn’t join the meeting in time is also not ideal!

Some additional context in the kernel commit description.

29 Likes

Thanks for being so proactive team!

2 Likes

literally just ran into this issue, figured out the quick-fix - half a minute later, i get a notification on my desktop that its already been fixed. thanks, garuda team, yall are great ^^

4 Likes

I am really suffering form not able to boot my system at first run , i had to make multiple start to get distro running , And important coding exams near by , hope it would be fixed now

Please make a separate forum post and provide as much information and logs as possible. The post you are replying to is not related to your issue.

1 Like

huhu bro after I sudo pacman -Syu I almost shut down my laptop because I wanted to log out, luckily I was careful, sorry I was slow to read the announcement and luckily I was able to reinstall Grub

… Reinstall grub?

Why?

Also, on Garuda Linux you should use garuda-update, not pacman -Syu.

4 Likes

The update failed to write to iniframs. After reboot i’m on emergency mode. What to do now? Also no 5g internet via usb cable.

1 Like

Please make a separate forum post and provide as much information and logs as possible.
Follow the template, please.

1 Like

ha ha , its quite strange , today again the boot system isnt working well , i am booting my laptop via recovery mode as in normal it isnt able to set init frames ,

Can you describe your issue more accurately?

A New member here but had an issue found great info in responses from a closed conversation back in May 2021. Seems when using the rani updater my system likes to hang, I found just bypassing that and using the CLI I dont get the same issue. I am running Broadwing versions on an hp victus gaming laptop i5 but my grandson decided to manage to break the screen on my other lappy. But Kudos to the support crew and the community I cant usually find a work around I’m now one happy grandmother

3 Likes

LOL folks here’s a HUGE warning don’t forget you Snapper support for Grub. Redid both my roommates machine and mine for some reason I forgot the files to allow snapshots on the Grub menu. I have one system that’s gone down because of this issue, and surprisingly the other is just fine even with getting the one message when doing updates. Considering the only real difference between the two machines is one is AM4 and one is AM5 everything installed on both is identical.

My BTRFS root partition, and the separate BTRFS home partition has been corrupted. Can I post my findings here for troubleshooting?

Would prefer a separate post that follows the issue post template.

BTRFS issue after updating to 6.15.7 - Issues & Assistance - Garuda Linux Forum

@TNE

Now recovery mode isnt able to start my laptop i mean , may be its my mistake and exam nearby i have to switch to other stable linux , it was on hope this machine turned on todayexam s nearby so :slightly_smiling_face: