From 4186441bbd912dea9c8a43dfd19dcbea90b4c3a0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= Date: Thu, 19 Dec 2019 10:42:14 +0100 Subject: Revert "cryptsetup: umount encrypted devices before detaching it during shutdown" This reverts commit 362c378291e85df3e00aaad491d1e08233ad127f. This commit introduced an ordering loop: remote-cryptsetup.target was both before and after remote-fs-pre.target. It also globally ordered all cryptsetup volumes before all mounts. Such global ordering is problematic if people have stacked storage. Let's look for a different solution. See https://github.com/systemd/systemd/pull/14378#discussion_r359460109. --- units/remote-fs-pre.target | 1 - 1 file changed, 1 deletion(-) (limited to 'units/remote-fs-pre.target') diff --git a/units/remote-fs-pre.target b/units/remote-fs-pre.target index b4a68c73dd..3f22605c8c 100644 --- a/units/remote-fs-pre.target +++ b/units/remote-fs-pre.target @@ -11,4 +11,3 @@ Description=Remote File Systems (Pre) Documentation=man:systemd.special(7) RefuseManualStart=yes -After=remote-cryptsetup.target -- cgit v1.2.1