Hello Coly! I think I can consistently reproduce a failure mode of bcache when going from 5.10 LTS to 5.15.2 - on one single system (my other systems do just fine). In 5.10, bcache is stable, no problems at all. After booting to 5.15.2, btrfs would complain about broken btree generation numbers, then freeze completely. Going back to 5.10, bcache complains about being broken and cannot start the cache set. I was able to reproduce the following behavior after the problem struck me twice in a row: 1. Boot into SysRescueCD 2. modprobe bcache 3. Manually detach the btrfs disks from bcache, set cache mode to none, force running 4. Reboot into 5.15.2 (now works) 5. See this error in dmesg: [ 27.334306] bcache: bch_cache_set_error() error on 04af889c-4ccb-401b-b525-fb9613a81b69: empty set at bucket 1213, block 1, 0 keys, disabling caching [ 27.334453] bcache: cache_set_free() Cache set 04af889c-4ccb-401b-b525-fb9613a81b69 unregistered [ 27.334510] bcache: register_cache() error sda3: failed to run cache set [ 27.334512] bcache: register_bcache() error : failed to register device 6. wipefs the failed bcache cache 7. bcache make -C -w 512 /dev/sda3 -l bcache-cdev0 --force 8. re-attach the btrfs disks in writearound mode 9. btrfs immediately fails, freezing the system (with transactions IDs way off) 10. reboot loops to 5, unable to mount 11. escape the situation by starting at 1, and not make a new bcache Is this a known error? Why does it only hit this machine? SSD Model: Samsung SSD 850 EVO 250GB Thanks, Kai
