-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Oops inside check_extent_to_backpointers during 1.13 → 1.18 upgrade #793
Comments
@g2p Could I just ask, how do you make the kernel show the relevant source files in backtraces? And the |
@thememika I get logs from journalctl or pstore (look at /usr/lib/tmpfiles.d/systemd-pstore.conf to enable), then I pipe them through |
I couldn't reproduce the bug, on the same kernel build (of a6c9019 merged with 6.12.1) the upgrade went through the next time I tried (also with fsck,fix_errors). Nothing particular in the logs for the successful mount, either.
|
The first time with the crash, I was mounting two filesystems at the same time, and the upgrades (from 1.13 to 1.18) were eating up memory. Next time, I was cautious and did them sequentially, another filesystem did its upgrade okay, the one that had crashed before crashed again near the end. And on a third boot, that filesystem was able to upgrade. So it might have been related to memory pressure. Btree usage: |
Link to another report of the same crash, also during the 1.13 to 1.18 upgrade: https://gist.github.com/noradtux/cb4f4a0234d2cd91871cb56714add986/ |
Tried to reproduce, downgrade went well, upgrade failed to mount with this error reported in dmesg:
|
Just pinged you on IRC - can you get me a metadata dump? There's some funny corruption going on, and this isn't showing up in my upgrade test. |
This is a filesystem that had a corrupted LRU, so I mounted it with fsck+fix_errors. Because I'm mounting from bcachefs-testing (a6c9019; merged with 6.12.1), it is also doing a version upgrade:
Here is the error in the LRU btree (at this point it was just the upgrade, no explicit fsck):
Next is trying again with fsck,fix_errors, a shift out of bounds, and an oops:
The text was updated successfully, but these errors were encountered: