This bug only affects zfs systems that have modified fstab without reloading systemd.
Essentially we run find on $boot_dir which is set as
# read available kernels from /boot
boot_dir="$(try_default_layout_bpool "${dataset}" "${mntdir}")"
if [ -z "${boot_dir}" ]; then boot_dir=$(get_system_directory "${dataset}" "boot" "false" "${mntdir}" "${etc_dir}")
fi
which somehow ends up being
'mount: (hint) your fstab has been modified, but systemd still uses\n the old version; use 'systemctl daemon-reload' to reload.\n/tmp/zfsmnt.liPzsI/boot'
It's not clear to me why the hint is on stdout in the first place.
This then causes the script to exit, which causes the trap to run which is broken due to bug 2031042.
This bug only affects zfs systems that have modified fstab without reloading systemd.
Essentially we run find on $boot_dir which is set as
# read available kernels from /boot dir="$( try_default_ layout_ bpool "${dataset}" "${mntdir}")"
boot_dir= $(get_system_ directory "${dataset}" "boot" "false" "${mntdir}" "${etc_dir}")
boot_
if [ -z "${boot_dir}" ]; then
fi
which somehow ends up being
'mount: (hint) your fstab has been modified, but systemd still uses\n the old version; use 'systemctl daemon-reload' to reload. \n/tmp/ zfsmnt. liPzsI/ boot'
It's not clear to me why the hint is on stdout in the first place.
This then causes the script to exit, which causes the trap to run which is broken due to bug 2031042.