In my case, they did not. On Tue, Apr 25, 2023 at 4:01 AM homerlinux <1969...@bugs.launchpad.net> wrote:
> May be, by any chance, that your zvols contain LVMs? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1969457 > > Title: > /dev/zvol links not created for encrypted zvols, zfs-volume-wait Timed > out waiting on zvol links > > Status in zfs-linux package in Ubuntu: > Confirmed > > Bug description: > Fresh installation of 20.04.4 with installer created zfs native > encrypted root > zfsutils-linux: 0.8.3-1ubuntu12.13 > > On reboot, zvol /dev/zvol entries are not being created. This seems to > effect different zvols each reboot. > > Example logs: > ``` > -- A start job for unit zsys-gc.service has finished successfully. > -- > -- The job identifier is 3139. > Apr 19 06:43:49 monolith zvol_wait[74768]: cannot open > 'rpool/export/vault/block': dataset does not exist > Apr 19 06:43:50 monolith zvol_wait[74786]: cannot open > 'rpool/export/vault/block': dataset does not exist > Apr 19 06:43:51 monolith zvol_wait[74805]: cannot open > 'rpool/export/vault/block': dataset does not exist > Apr 19 06:43:52 monolith zvol_wait[74823]: cannot open > 'rpool/export/vault/block': dataset does not exist > Apr 19 06:43:53 monolith zvol_wait[74932]: cannot open > 'rpool/export/vault/block': dataset does not exist > Apr 19 06:43:54 monolith zvol_wait[74950]: cannot open > 'rpool/export/vault/block': dataset does not exist > Apr 19 06:43:55 monolith zvol_wait[74969]: cannot open > 'rpool/export/vault/block': dataset does not exist > Apr 19 06:43:56 monolith zvol_wait[74987]: cannot open > 'rpool/export/vault/block': dataset does not exist > Apr 19 06:43:57 monolith zvol_wait[75006]: cannot open > 'rpool/export/vault/block': dataset does not exist > Apr 19 06:43:58 monolith zvol_wait[4440]: Still waiting on 1 zvol links > ... > Apr 19 06:43:58 monolith zvol_wait[4440]: No progress since last loop. > Apr 19 06:43:58 monolith zvol_wait[4440]: Checking if any zvols were > deleted. > Apr 19 06:43:58 monolith zvol_wait[4440]: Remaining zvols: > Apr 19 06:43:58 monolith zvol_wait[4440]: > rpool/libvirt_zvols/kube-04-disk0 > Apr 19 06:43:58 monolith zvol_wait[4440]: Timed out waiting on zvol links > Apr 19 06:43:58 monolith systemd[1]: zfs-volume-wait.service: Main > process exited, code=exited, status=1/FAILURE > -- Subject: Unit process exited > -- Defined-By: systemd > -- Support: http://www.ubuntu.com/support > -- > -- An ExecStart= process belonging to unit zfs-volume-wait.service has > exited. > -- > -- The process' exit code is 'exited' and its exit status is 1. > Apr 19 06:43:58 monolith systemd[1]: zfs-volume-wait.service: Failed > with result 'exit-code'. > -- Subject: Unit failed > -- Defined-By: systemd > -- Support: http://www.ubuntu.com/support > -- > -- The unit zfs-volume-wait.service has entered the 'failed' state with > result 'exit-code'. > Apr 19 06:43:58 monolith systemd[1]: Failed to start Wait for ZFS Volume > (zvol) links in /dev. > -- Subject: A start job for unit zfs-volume-wait.service has failed > -- Defined-By: systemd > -- Support: http://www.ubuntu.com/support > -- > -- A start job for unit zfs-volume-wait.service has finished with a > failure. > -- > -- The job identifier is 226 and the job result is failed. > Apr 19 06:43:58 monolith systemd[1]: Dependency failed for ZFS volumes > are ready. > -- Subject: A start job for unit zfs-volumes.target has failed > -- Defined-By: systemd > -- Support: http://www.ubuntu.com/support > -- > -- A start job for unit zfs-volumes.target has finished with a failure. > ``` > I believe this is related to changes made here: > https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1888405 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1969457/+subscriptions > > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1969457 Title: /dev/zvol links not created for encrypted zvols, zfs-volume-wait Timed out waiting on zvol links Status in zfs-linux package in Ubuntu: Confirmed Bug description: Fresh installation of 20.04.4 with installer created zfs native encrypted root zfsutils-linux: 0.8.3-1ubuntu12.13 On reboot, zvol /dev/zvol entries are not being created. This seems to effect different zvols each reboot. Example logs: ``` -- A start job for unit zsys-gc.service has finished successfully. -- -- The job identifier is 3139. Apr 19 06:43:49 monolith zvol_wait[74768]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:50 monolith zvol_wait[74786]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:51 monolith zvol_wait[74805]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:52 monolith zvol_wait[74823]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:53 monolith zvol_wait[74932]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:54 monolith zvol_wait[74950]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:55 monolith zvol_wait[74969]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:56 monolith zvol_wait[74987]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:57 monolith zvol_wait[75006]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:58 monolith zvol_wait[4440]: Still waiting on 1 zvol links ... Apr 19 06:43:58 monolith zvol_wait[4440]: No progress since last loop. Apr 19 06:43:58 monolith zvol_wait[4440]: Checking if any zvols were deleted. Apr 19 06:43:58 monolith zvol_wait[4440]: Remaining zvols: Apr 19 06:43:58 monolith zvol_wait[4440]: rpool/libvirt_zvols/kube-04-disk0 Apr 19 06:43:58 monolith zvol_wait[4440]: Timed out waiting on zvol links Apr 19 06:43:58 monolith systemd[1]: zfs-volume-wait.service: Main process exited, code=exited, status=1/FAILURE -- Subject: Unit process exited -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- An ExecStart= process belonging to unit zfs-volume-wait.service has exited. -- -- The process' exit code is 'exited' and its exit status is 1. Apr 19 06:43:58 monolith systemd[1]: zfs-volume-wait.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- The unit zfs-volume-wait.service has entered the 'failed' state with result 'exit-code'. Apr 19 06:43:58 monolith systemd[1]: Failed to start Wait for ZFS Volume (zvol) links in /dev. -- Subject: A start job for unit zfs-volume-wait.service has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit zfs-volume-wait.service has finished with a failure. -- -- The job identifier is 226 and the job result is failed. Apr 19 06:43:58 monolith systemd[1]: Dependency failed for ZFS volumes are ready. -- Subject: A start job for unit zfs-volumes.target has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit zfs-volumes.target has finished with a failure. ``` I believe this is related to changes made here: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1888405 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1969457/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
