FS#64216 - [btrfs-progs] undefined symbol in libbtrfs.so

Attached to Project: Arch Linux
Opened by Philipp Wolfer (phw) - Tuesday, 22 October 2019, 14:16 GMT
Last edited by Sébastien Luttringer (seblu) - Thursday, 31 October 2019, 08:36 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Sébastien Luttringer (seblu)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 17
Private No

Details

Description:
Since the update to btrfs-progs 0.60.8-1 running snapper gives a symbol lookup error.

Additional info:
* snapper 0.8.4-1
* btrfs-progs 0.60.8-1

Steps to reproduce:
$ snapper --version
snapper: symbol lookup error: /usr/lib/libbtrfs.so.0: undefined symbol: write_raid56_with_parity
This task depends upon

Closed by  Sébastien Luttringer (seblu)
Thursday, 31 October 2019, 08:36 GMT
Reason for closing:  Fixed
Comment by Philipp Wolfer (phw) - Tuesday, 22 October 2019, 14:18 GMT
Sorry for the missing summary. Flyspray UI is horrible, but I can't change it.
Comment by Sébastien Luttringer (seblu) - Tuesday, 22 October 2019, 14:40 GMT
Looks like a problem with snapper and not btrfs.

You are reporting btrfs-progs 0.60.8-1. Last version is 5.3-1. Are you from the past?

Comment by Philipp Wolfer (phw) - Tuesday, 22 October 2019, 14:43 GMT
Sorry, that's just me not being able to parse the pacman output properly. 5.3-1 that is.

I assume also this is a snapper problem, that's why I originally reported this for the [snapper] package.
Comment by Antonio Rojas (arojas) - Tuesday, 22 October 2019, 14:44 GMT
@seblu no, the undefined symbol is in libbtrfs.so
Comment by Sébastien Luttringer (seblu) - Tuesday, 22 October 2019, 16:00 GMT
@arojas: correct. damn! ;)

I reported it upstreams: https://github.com/kdave/btrfs-progs/issues/214
Comment by Eli Schwartz (eschwartz) - Wednesday, 23 October 2019, 02:38 GMT
Sounds like a similar story to  FS#61499 , so if snapper ever fails due to missing symbols in libbtrfs.so I'll just be assuming from here on out that there is a bug in the btrfs-progs build system. ;)
Comment by Sébastien Luttringer (seblu) - Wednesday, 23 October 2019, 16:49 GMT
A bit edge, but I added the patch from this merge request: https://github.com/kdave/btrfs-progs/pull/215 into testing.
Comment by Julien Noblet (skiltz) - Wednesday, 23 October 2019, 16:51 GMT
@Sébastien Luttringer (seblu), you should use https://github.com/kdave/btrfs-progs/pull/216
Comment by Sébastien Luttringer (seblu) - Wednesday, 23 October 2019, 17:25 GMT
I did, see https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/btrfs-progs&id=9cc711a30244c2726e8d94dcd180fd13fd3641f3
Comment by Julien Noblet (skiltz) - Wednesday, 23 October 2019, 17:27 GMT
@seblu ;)
Comment by Luflosi (Luflosi) - Wednesday, 23 October 2019, 17:34 GMT
I can no longer reproduce the issue with btrfs-progs 5.3-2 from testing 🎉.
Comment by Michael Beck (mbk) - Wednesday, 23 October 2019, 18:32 GMT
Can confirm. Also switching back to btrfs-progs 5.2.2-1 the message no longer appears.
Comment by Philipp Wolfer (phw) - Thursday, 24 October 2019, 09:03 GMT
I can also confirm the patched version works, thanks for acting on this so quickly.
Comment by Markus Hartung (harre) - Thursday, 24 October 2019, 21:04 GMT
I tried the btrfs-progs-git aur-package and it doesn't seem to include the patch.
Comment by loqs (loqs) - Thursday, 24 October 2019, 21:31 GMT
@harre see https://github.com/kdave/btrfs-progs/pull/216#issuecomment-545687093
Comment by Ben White (biwhite) - Friday, 25 October 2019, 13:06 GMT
https://github.com/kdave/btrfs-progs/releases/tag/v5.3.1 has the fix apparently

Loading...