Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#78895 - System upgrade breaks the whole system

Attached to Project: Arch Linux
Opened by Niccolò Belli (darkbasic) - Monday, 26 June 2023, 15:21 GMT
Last edited by Andreas Radke (AndyRTR) - Monday, 26 June 2023, 16:06 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Hi,
On Friday 23 I attempted a system upgrade which rendered my whole system completely unusable (in the middle of the update the system couldn't even execute the existing binaries). Since I use btrfs snapshots today I've rolled back and attempted the update again, but it's the same story.
The system was a couple of days (weeks at most) old.
What's happening? I can rollback again and give you all the info you need about the state of the system before the upgrade.

pacman -Syu log: https://pastebin.com/Qjfk3u70

dmesg after pacman -Syu

[ 270.762819] systemd[1]: systemd 253.5-2-arch running in system mode (+PAM +AUDIT -SELINUX -APPARMOR -IMA +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT -QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK +XKBCOMMON +UTMP -SYSVINIT default-hierarchy=unified)
[ 270.762946] systemd[1]: Detected architecture x86-64.
[ 270.919560] systemd[1]: bpf-lsm: LSM BPF program attached
[ 312.069489] BTRFS info: devid 1 device path /dev/mapper/cryptroot changed to /dev/dm-0 scanned by (udev-worker) (5365)
[ 312.070420] BTRFS info: devid 1 device path /dev/dm-0 changed to /dev/mapper/cryptroot scanned by (udev-worker) (5365)
[ 319.396280] modinfo[7621]: segfault at ffffffffffffffb8 ip 00007fe3a7cadc5e sp 00007ffec7789d50 error 5 in libc.so.6[7fe3a7c38000+15d000] likely on CPU 1 (core 1, socket 0)
[ 319.396291] Code: 66 2e 0f 1f 84 00 00 00 00 00 66 90 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d da 30 14 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 58 30 14 00 64 48 83 3a
[ 326.088362] modinfo[11207]: segfault at ffffffffffffffb8 ip 00007fc1248adc5e sp 00007fffc9f368b0 error 5 in libc.so.6[7fc124838000+15d000] likely on CPU 1 (core 1, socket 0)
[ 326.088373] Code: 66 2e 0f 1f 84 00 00 00 00 00 66 90 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d da 30 14 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 58 30 14 00 64 48 83 3a
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Monday, 26 June 2023, 16:06 GMT
Reason for closing:  Not a bug
Comment by Doug Newgard (Scimmia) - Monday, 26 June 2023, 15:53 GMT
This is a support issue, specific to your system. You're best off using the support channels: forums, IRC, and mailing lists.
Comment by Niccolò Belli (darkbasic) - Monday, 26 June 2023, 15:53 GMT
Wow, I think I've found what's the issue at play... There was not enough disk space and this is how btrfs behaves in such scenario. I've rolled back, cleaned up some space and performed the upgrade again: no issue at all.

Loading...