Random FS issues on OSTree images

Affected images versions

• not relevant (explain why)
• see the table below (list the build id and the apt or ostree deployment of the tested images in the appropriate cells)

Type	Arch	v2021	v2022	v2023dev3
minimal/fixedfunction	amd64		x	x
minimal/fixedfunction	armhf		x	x
minimal/fixedfunction	arm64		x	x
target/hmi	amd64		x	x
target/hmi	armhf		x	x
target/hmi	arm64		x	x
basesdk	amd64
sdk	amd64
nfs	amd64
nfs	armhf
nfs	arm64
lxc	amd64
lxc	armhf
lxc	arm64
image-builder
package-source-builder

Release v2022 and v2023dev1 Type: OSTree

Unaffected images versions

Issue on APT images is not confirmed, likely because we do not have tests that exercise unclean resets on them.

Testcase

The updater testcases, which do several unclean reboots in a single run.

Steps to reproduce

There are not specific steps, some test fail due to FS issues

Expected result

Actual result

[   94.467095] EXT4-fs error (device mmcblk1p2): __ext4_find_entry:1623: inode #32915: comm pool: checksumming directory block 0
[   94.479310] EXT4-fs error (device mmcblk1p2): __ext4_find_entry:1623: inode #32915: comm pool: checksumming directory block 0
AUM-Message: 18:13:18.535: Upgrade status: Unknown
May 16 18:13:18 apertis apertis-update-managerd[636]: Transaction complete; bootconfig swap: yes; deployment count change: 1
May 16 18:13:18 apertis apertis-update-[636]: Cleanup problem: Generating deployment refs: Listing refs: fstatat(refs/heads/ostree/0/0): Bad message
May 16 18:13:18 apertis apertis-update-[636]: Ostree upgrade failed: Performing final cleanup: Generating deployment refs: Listing refs: fstatat(refs/heads/ostree/0/0): Bad message

EBADMSG is ext4 finding a broken CRC.

Reproducibility

How often the issue is hit when repeating the test and changing nothing (same device, same image, etc.)?

Put the ✅ in the most appropriate entry:

1. always
2. often, but not always
3. ✅ rarely

Impact of bug

Some tests fails due to random FS issues, this has been seen in OSTree images so far. Initial comments can be found in {T8547}

Attachments

Root cause

TBD

Outcomes

• v2023:
  • kernel: pkg/linux!160 (merged)
  • debos: pkg/debos!24 (closed)
• v2022:
  • kernel: pkg/linux!162 (merged)
• upstream:
  • debos: https://github.com/go-debos/debos/pull/334

Management data

This section is for management only, it should be the last one in the description.

Phabricator link: https://phabricator.apertis.org/T8660