Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: systemd (Ubuntu Eoan)
       Status: New => Confirmed

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

Title:
  systemd journald failed unmounting var

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Bionic:
  Confirmed
Status in systemd source package in Cosmic:
  Confirmed
Status in systemd source package in Disco:
  Confirmed
Status in systemd source package in Eoan:
  Confirmed

Bug description:
  [impact]

  on a system with /var and/or /var/log mounted separately from /,
  shutdown can't unmount /var (or /var/log) cleanly because systemd-
  journald is using it.

  [test case]

  install a system with /var mounted separately from /

  shutdown, and notice:

  [FAILED] Failed unmounting /var.

  [regression potential]

  TBD

  [other info]

  original description:

  --

  When the system is shut down or restarted the systemd-journal does not
  disassemble the disks correctly.

  On this thread https://unix.stackexchange.com/questions/378678/why-
  do-i-get-the-error-failed-unmounting-var-during-shutdown

  I checked what editing /etc/systemd/journald.conf
  to change the Storage = line to Storage = volatile the problem is solved, but 
some of the logs on the shutdown are lost.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Mon Aug 20 18:15:07 2018
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2018-08-20 (0 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=65cb761b-4881-4031-9113-e6bb6a1437b4 ro
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  mtime.conffile..etc.systemd.journald.conf: 2018-08-20T18:00:58.586165

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to