fstrim: do not use Protect setting in systemd service

The ProtectHome= and ProtectSystem= settings mounts all stuff for the service in read-only mode. The fstrim ioctl operates on read-only mountpoint file descriptor, but on some read-only filesystem the operation can fail, so since 2d22ac6 we check for read-only volumes and skip it. References: Upstream: http://github.com/karelzak/util-linux/commit/2d22ac64e4d6e6732640f38b7232b5bcdc84a877 Addresses: #948 Signed-off-by: Karel Zak <kzak@redhat.com>
util-linux · Feb 4, 2020 · 61b384b · 61b384b
1 parent 00e53f1
commit 61b384b
Showing 1 changed file with 0 additions and 2 deletions.
diff --git a/sys-utils/fstrim.service.in b/sys-utils/fstrim.service.in
@@ -6,8 +6,6 @@ ConditionVirtualization=!container
 [Service]
 Type=oneshot
 ExecStart=@sbindir@/fstrim --fstab --verbose --quiet
-ProtectSystem=strict
-ProtectHome=read-only
 PrivateDevices=no
 PrivateNetwork=yes
 PrivateUsers=no