Comment 9 for bug 1844195

Really curious if this turns out to be a glibc problem or a beegfs-meta problem, but we were able to hack together something that circumvents this problem by forcing beegfs-meta to use an older glibc6 (from xenial). beegfs-meta is now stable and performing much better!

There's probably a simpler way to do this, but we did something along these lines:

1. debootstrap xenial /srv/xenial-chroot
2. chroot into xenial-chroot, add beegfs to apt sources.list, apt install beegfs-meta, exit chroot
3. prepare a systemd pre-exec script "/usr/local/bin/setup-beegfs-meta-chroot.sh":

#!/bin/bash

set -e

cp /etc/beegfs/beegfs-meta.conf /srv/xenial-chroot/etc/beegfs/beegfs-meta.conf
mountpoint -q /srv/xenial-chroot/proc || mount --bind /proc /srv/xenial-chroot/proc
mountpoint -q /srv/xenial-chroot/sys || mount --bind /sys /srv/xenial-chroot/sys
mountpoint -q /srv/xenial-chroot/path/to/metadata || mount --bind /path/to/metadata /srv/xenial-chroot/path/to/metadata

4. copy /lib/systemd/system/beegfs-meta.service to /etc/systemd/system/beegfs-meta.service, adding the following to the [service] section:

RootDirectory=/srv/xenial-chroot
ExecStartPre=/usr/local/bin/setup-beegfs-meta-chroot.sh
RootDirectoryStartOnly=yes

5. daemon-reload systemd and restart beeegfs-meta