touch-packages team mailing list archive

[Steve Langasek <steve.langasek@xxxxxxxxxxxxx>]

The masking of mountall when booting with systemd is deliberate;
mountall is a component of upstart's boot system and should not be used
with systemd.

So if there are any problems with mounting filesystems at boot when
booting with systemd, that's a systemd bug.  Reassigning.

** Package changed: mountall (Ubuntu) => systemd (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1432123

Title:
  mountall service unavailable on systemd, preventing full zfs
  integration

Status in systemd package in Ubuntu:
  New

Bug description:
  I am test-driving Vivid and made the switch to systemd. I'd like to
  report that the mountall service is now unavailable.

  root# systemctl status mountall
   mountall.service
     Loaded: masked (/dev/null)
     Active: inactive (dead)

  root# ll /lib/systemd/system/mountall.service
  lrwxrwxrwx 1 root root 9 Mar 11 11:22 /lib/systemd/system/mountall.service -> /dev/null

  Per https://github.com/zfsonlinux/pkg-zfs/issues/132 I assume this is
  what is keeping all of my zfs filesystems from being automounted at
  boot.

  Things worked fine with upstart.

  zfs-pkg bug report: https://github.com/zfsonlinux/pkg-zfs/issues/145
  systemd bug report: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432122

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432123/+subscriptions