about summary refs log tree commit diff
path: root/machines/aszlig
diff options
context:
space:
mode:
authoraszlig <aszlig@nix.build>2021-01-04 10:18:51 +0100
committeraszlig <aszlig@nix.build>2021-01-04 10:23:55 +0100
commit4dc099f51af33c7c9d1d984887e0dcbf6fa9e04b (patch)
tree7416aface021d38d41c9c5a014b1983db0430067 /machines/aszlig
parent38048dc207920a41356ff9e99e473835f699cd05 (diff)
dnyarri: Fix unit names for btrfs scrub services
Injecting pre/post start scripts into services called
"btrfs-scrub-.service.service" isn't going to do a whole lot if the
actual service name is called "btrfs-scrub-.service".

During the last scrub I was wondering why caching got slow afterwards
and found out that the caching devices were filled with lots of
irrelevant data from the scrub. This led me to inspect what went wrong
and when checking the properties of the scrub service unit, I found out
that it never worked in the first place for the reason meantioned in the
first paragraph.

Actually using the right unit name helps a lot here, so onwards to the
next scrub in February :-)

Signed-off-by: aszlig <aszlig@nix.build>
Diffstat (limited to 'machines/aszlig')
-rw-r--r--machines/aszlig/dnyarri.nix2
1 files changed, 1 insertions, 1 deletions
diff --git a/machines/aszlig/dnyarri.nix b/machines/aszlig/dnyarri.nix
index 3effb1b0..e61fe517 100644
--- a/machines/aszlig/dnyarri.nix
+++ b/machines/aszlig/dnyarri.nix
@@ -109,7 +109,7 @@ in {
   # services, so we don't get large amounts of nonsense on the caching device.
   systemd.services = let
     scrubServiceUnits = let
-      mkName = fs: "btrfs-scrub-${utils.escapeSystemdPath fs}.service";
+      mkName = fs: "btrfs-scrub-${utils.escapeSystemdPath fs}";
     in map mkName config.services.btrfs.autoScrub.fileSystems;
   in lib.genAttrs scrubServiceUnits (lib.const {
     preStart = bcacheStop;