From: Michael Marineau <michael.marineau@coreos.com>
Date: Fri, 13 Nov 2015 02:10:57 +0000 (-0800)
Subject: generator: order initrd fsck-root after local-fs-pre
X-Git-Tag: v228~39^2
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=5fd534d919c0dc94db05cf6661d3f4819f2d7b22;p=platform%2Fupstream%2Fsystemd.git

generator: order initrd fsck-root after local-fs-pre

The initrd version of systemd-fsck-root.service must wait for
local-fs-pre.target just like systemd-fsck@.service to prevent
modifications to the filesystem prior to resuming from hibernation.
As-is my laptop routinely fails to resume due to fsck errors. The rest
of the time it is probably silently corrupting the filesystem.

Unlike normal boot, in the initrd systemd-fsck-root.service has no
special significance so it needs to be kept in sync with
systemd-fsck@.service. The name systemd-fsck-root.service is only used
to preserve state across switch-root.
---

diff --git a/src/shared/generator.c b/src/shared/generator.c
index cb4ebc6..b3c22ff 100644
--- a/src/shared/generator.c
+++ b/src/shared/generator.c
@@ -64,7 +64,7 @@ static int write_fsck_sysroot_service(const char *dir, const char *what) {
                 "Description=File System Check on %2$s\n"
                 "DefaultDependencies=no\n"
                 "BindsTo=%3$s\n"
-                "After=%3$s\n"
+                "After=%3$s local-fs-pre.target\n"
                 "Before=shutdown.target\n"
                 "\n"
                 "[Service]\n"