touch-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

The archive grep for 12.04 (precise) is done. I see a bunch of (now
outdated) documentation wrt. /dev/cgroup, particularly in the kernel
sources and in libvirt. ltp also uses it heavily in its test suite. But
aside from that there is no maintainer script, installer, or other thing
which would create this fstab entry.

archive grep for 10.04 (lucid) is still ongoing, but I don't expect a
match there (there's none so far). So I figure this fstab line was added
by some third-party package or manually?

Note that in the case of nonexisting fstab entries you are supposed to
get a friendly-recovery menu or an emergency shell. This doesn't
currently happen, which is perhaps the main issue here? This is being
tracked in bug 1471258.

** Attachment added: "precise archive grep for /dev/cgroup"
   https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1460794/+attachment/4425717/+files/cgroup-precise.out

-- 
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/1460794

Title:
  boot fails if /dev/cgroup fstab entry is present

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I recently upgraded a server from 14.10 to 15.04. The upgrade claim to
  have worked but the system could not boot afterwards.

  Basically when you attempt to reboot you end up at an emergency maintenance prompt early in the boot process.
  After a lot of digging one of the messages in the logs gives:
  systemd[1]: /usr appears to be on its own filesystem and is not already mounted. This is not a supported setup. Some things will probably break (sometimes even silently) in mysterious ways. Consult http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken

  Basically systemd cannot deal with /usr being on a separate partition.
  That needs to be fixed or systemd should not be used for upgrades with
  a separate /usr partition.

  This is related to bug 1460790 but asking for systemd to actually be fixed.
  Please see bug 1460790 if you are looking for a work around on this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu5
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  Date: Mon Jun  1 15:29:32 2015
  InstallationDate: Installed on 2010-05-23 (1835 days ago)
  InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
  MachineType: Supermicro X8STi
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_CA.UTF-8
   SHELL=/bin/tcsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic root=UUID=676235cd-93b1-426e-8336-fa0078d96145 ro quiet acpi=off pci=noacpi
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-06-01 (0 days ago)
  dmi.bios.date: 09/17/10
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.0
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: X8STi
  dmi.board.vendor: Supermicro
  dmi.board.version: 1234567890
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0:bd09/17/10:svnSupermicro:pnX8STi:pvr1234567890:rvnSupermicro:rnX8STi:rvr1234567890:cvnSupermicro:ct3:cvr1234567890:
  dmi.product.name: X8STi
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro

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