[Bug 1982486] Re: update-motd-fsck-at-reboot: exclude nbd devices

[Launchpad Bug Tracker]

** Merge proposal linked:
   https://code.launchpad.net/~oddbloke/update-notifier/+git/update-notifier/+merge/427497

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-notifier in Ubuntu.
https://bugs.launchpad.net/bugs/1982486

Title:
  update-motd-fsck-at-reboot: exclude nbd devices

Status in update-notifier package in Ubuntu:
  In Progress

Bug description:
  I've ended up in a situation where a machine's /dev/nbd* devices are
  in a broken state: the easiest way for me to fix this is to reboot the
  system.  However, the reboot is blocked by update-motd-fsck-at-reboot
  trying to run dumpe2fs against one of the broken partitions:

  $ ps faux
  ...
  root      191396  0.0  0.2  37864  8672 ?        Ss   12:37   0:00 sshd: dwatkins [priv]
  root      191421  0.0  0.0   2608   480 ?        S    12:37   0:00  \_ sh -c /usr/bin/env -i PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin run-parts --ls
  root      191422  0.0  0.0   2496   508 ?        S    12:37   0:00      \_ run-parts --lsbsysinit /etc/update-motd.d
  root      191455  0.0  0.0   2608  1748 ?        S    12:37   0:00          \_ /bin/sh /usr/lib/update-notifier/update-motd-fsck-at-reboot
  root      191483  0.0  0.0   3480   944 ?        D    12:37   0:00              \_ dumpe2fs -h /dev/nbd0p2
  ...

  These NBD devices will not be present after a reboot, so I think the
  script would probably be more correct if it omitted operating on these
  devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1982486/+subscriptions