FS#76266 - [inux] 6.0.3 breaks boot on btrfs with space_cache version 1

Attached to Project: Arch Linux
Opened by Tobias Powalowski (tpowa) - Saturday, 22 October 2022, 15:56 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 26 October 2022, 16:31 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture All
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Hi,
latest kernel in testing breaks boot on 6.0.3:
https://pkgbuild.com/~tpowa/IMG-6839.JPG

To solve the issue:
mount your btrfs filesystem with clear_cache,space_cache=v2 option one time.
Either on bootloader or in fstab you need to use this options or downgrade to kernel 6.0.2.
By using this way your space cache is converted to version 2, which is the default since kernel 5.15.

6.0.5 reverts the commit that causes that issue.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Wednesday, 26 October 2022, 16:31 GMT
Reason for closing:  Fixed
Additional comments about closing:  6.0.5-1 in testing
Comment by wtf (oi_wtf) - Monday, 24 October 2022, 20:54 GMT
For me it got stuck when mounting the second to last btrfs filesystem to be mounted on the system.
Way later than in tpowa's case, but it still got stuck.
The system has 5 distinct btrfs filesystems, all had space_cache v1. only when mounting the 4th, it got stuck.
( the 5th gets automounted on demand, so that's probably why it does not get involved here)

It also complained about cpu being stuck, same backtrace and switching to spache_cache v2 workaround helped.
Comment by Christoph Anton Mitterer (calestyo) - Monday, 24 October 2022, 21:04 GMT
Just for the records... I had some more or less similar issue just the other day, described here:
2291416ef48d98059f9fdc5d865b0ff040148237.camel@scientia.org/T/#u"> https://lore.kernel.org/linux-btrfs/2291416ef48d98059f9fdc5d865b0ff040148237.camel@scientia.org/T/#u

Also on 6.0.3 ... though at least one part of it, worked later on 6.0.3.
Comment by Tobias Powalowski (tpowa) - Tuesday, 25 October 2022, 13:17 GMT
Got an answer from gregkh this issue will be fixed in 6.0.4 round.
https://lore.kernel.org/all/Y1aeWdHd4%2FluzhAu%40localhost.localdomain/
Comment by Tobias Powalowski (tpowa) - Wednesday, 26 October 2022, 15:35 GMT

Loading...