[Bug 1701875] [NEW] systemd crashing swap partitions

Hadmut Danisch hadmut at danisch.de
Sun Jul 2 07:22:42 UTC 2017 

Public bug reported:

Hi,

systemd still kills the swap device sometimes.

I typically avoid lvm and prefer the partition scheme like

/dev/sda1   unencrypted boot
/dev/sda2   luks-encrypted swap
/dev/sda3   luks-encrypted /root


and haven an /etc/crypttab like

sda2_crypt UUID=a5b1de14-00e7-46a2-a18a-118af13d0ea7 none luks,swap,discard
sda3_crypt UUID=9ec0971c-605f-4045-a8e4-57f15c933441 none luks,discard


Since using systemd it sometimes happens that the system does not boot anymore. Analysis shows that for some reason the swap partition (the raw partition before encryption) contains just rubbish, and since systemd insists on getting this swap device for dependencies and thus never fulfills it's dependencies. 

I have no idea what happens insided that damned systemd, since I did not
found any debugging method to see what systemd does. If /etc/crypttab
contains a swap tag, systemd tries to run mkswap and something goes
wrong every now and then (not always, most of the time it works as
expected).

My current guess is that there is some race condition between the normal
mount and recreating the swap, and it looks as if systemd has
dependencies twice, for the device name (sda2 and sda2_crypt) and the
UUID, maybe two processes are spawned instead of one and interfere.

However, it makes systems unstable and unreliable.

regards

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu17
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Jul  2 09:06:42 2017
MachineType: Medion G24
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic root=UUID=4638a5a1-629c-477c-b1df-b370d0181be5 ro rootflags=subvol=@ splash quiet
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
 [EXTENDED]   /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf
 
 2 overridden configuration files found.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/12/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: H61TIW08.111
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61H2-TI2
dmi.board.vendor: Medion
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Medion
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrH61TIW08.111:bd10/12/2012:svnMedion:pnG24:pvr1.0:rvnMedion:rnH61H2-TI2:rvr1.0:cvnMedion:ct3:cvr1.0:
dmi.product.name: G24
dmi.product.version: 1.0
dmi.sys.vendor: Medion

** Affects: systemd (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  systemd crashing swap partitions

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,

  systemd still kills the swap device sometimes.

  I typically avoid lvm and prefer the partition scheme like

  /dev/sda1   unencrypted boot
  /dev/sda2   luks-encrypted swap
  /dev/sda3   luks-encrypted /root

  
  and haven an /etc/crypttab like

  sda2_crypt UUID=a5b1de14-00e7-46a2-a18a-118af13d0ea7 none luks,swap,discard
  sda3_crypt UUID=9ec0971c-605f-4045-a8e4-57f15c933441 none luks,discard

  
  Since using systemd it sometimes happens that the system does not boot anymore. Analysis shows that for some reason the swap partition (the raw partition before encryption) contains just rubbish, and since systemd insists on getting this swap device for dependencies and thus never fulfills it's dependencies. 

  I have no idea what happens insided that damned systemd, since I did
  not found any debugging method to see what systemd does. If
  /etc/crypttab contains a swap tag, systemd tries to run mkswap and
  something goes wrong every now and then (not always, most of the time
  it works as expected).

  My current guess is that there is some race condition between the
  normal mount and recreating the swap, and it looks as if systemd has
  dependencies twice, for the device name (sda2 and sda2_crypt) and the
  UUID, maybe two processes are spawned instead of one and interfere.

  However, it makes systems unstable and unreliable.

  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu17
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Jul  2 09:06:42 2017
  MachineType: Medion G24
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic root=UUID=4638a5a1-629c-477c-b1df-b370d0181be5 ro rootflags=subvol=@ splash quiet
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: H61TIW08.111
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61H2-TI2
  dmi.board.vendor: Medion
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Medion
  dmi.chassis.version: 1.0
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrH61TIW08.111:bd10/12/2012:svnMedion:pnG24:pvr1.0:rvnMedion:rnH61H2-TI2:rvr1.0:cvnMedion:ct3:cvr1.0:
  dmi.product.name: G24
  dmi.product.version: 1.0
  dmi.sys.vendor: Medion

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

More information about the foundations-bugs mailing list