[Bug 1788048] Re: systemd journald failed unmounting var
C de-Avillez
hggdh2 at ubuntu.com
Sun Sep 23 21:58:24 UTC 2018
Updated with upstream bug #; this seems to be an on-going concern, and
depends on some not-yet-available interfaces between kernel and systemd.
Marking Triaged/Medium. There are some bypasses discussed in the
upstream bug, but not all possible effects have already been discussed
(for example, setting 'storage=volatile' completely loses the journald
logs at shutdown).
** Bug watch added: github.com/systemd/systemd/issues #867
https://github.com/systemd/systemd/issues/867
** Also affects: systemd via
https://github.com/systemd/systemd/issues/867
Importance: Unknown
Status: Unknown
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1788048
Title:
systemd journald failed unmounting var
Status in systemd:
Unknown
Status in systemd package in Ubuntu:
Triaged
Bug 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 at .service → /lib/systemd/system/user at .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
More information about the foundations-bugs
mailing list