Filesystem automatically mounted when specific service is killed in Red Hat Enterprise Linux

Issue

• We had the problem, that systemd auto-mounted an old filesystem.

• We are seeing a filesystem being mounted after killing an application process, even though, the mount was umounted after killing the process. In the logs, the following information are found:

  Jul 07 16:39:38 server.example.com systemd[1]: Started Example Service.
  Jul 07 16:39:38 server.example.com systemd[1]: Starting Example Service...
  Jul 07 16:39:38 server.example.com systemd[1]: example.service: main process exited, code=exited, status=200/CHDIR
  Jul 07 16:39:38 server.example.com systemd[64873]: Failed at step CHDIR spawning /bin/kill: No such file or directory
  Jul 07 16:39:38 server.example.com systemd[1]: example.service: control process exited, code=exited status=200
  Jul 07 16:39:38 server.example.com systemd[1]: Unit example.service entered failed state.
  Jul 07 16:39:38 server.example.com systemd[1]: example.service failed.
  [...]
  Jul 07 16:40:38 server.example.com systemd[1]: example.service holdoff time over, scheduling restart.
  Jul 07 16:40:38 server.example.com systemd[1]: example-test.mount: Directory /example/test to mount over is not empty, mounting anyway.
  Jul 07 16:40:38 server.example.com systemd[1]: Mounting /example/test...