Levi Zim (5e82cb79) at 12 Dec 15:21

... and 228 more commits

Levi Zim (bc24f617) at 01 Dec 11:53

Levi Zim (059e1aa1) at 02 Jul 12:06

Levi Zim (47a1358d) at 02 Jul 04:39

... and 82 more commits

Levi Zim (9f58842d) at 14 Mar 23:52

... and 6 more commits

Thanks for your detailed explanation ☺️! I will change this PR to use a persistent directory.

Do you prefer to keep this directory in mailDirectory and exclude it from borg, or just use a persistent directory outside mailDirectory like /var/vmail-borg?

Levi Zim (34008397) at 31 Jan 05:44

Is it not an issue to cleanup this borg directory at each run?

I think cleanup this borg directory will also solve this issue. But fundamentally this issue is caused by borg backing up a directory /var/vmail that itself also writes to (/var/vmail/.config/borg). So my proposed solution here is to let borg writes to a private /tmp instead.

(i presume the private tmp directory is cleaned up by systemd each time the service is stopped).

Yes

borg writes to $HOME/.config but in our case it also works on $HOME (/var/vmail).

This could cause the following error when running the backup: file changed while we backed it up

× borgbackup.service - borgbackup
     Loaded: loaded (/etc/systemd/system/borgbackup.service; linked; preset: ignored)
    Drop-In: /nix/store/8iqfrm23vqm9vb4dhfrkm2gp53rhds65-system-units/service.d
             └─10-all-failure-handler.conf
     Active: failed (Result: exit-code) since Tue 2025-01-21 11:00:14 UTC; 54ms ago
   Duration: 11.283s
 Invocation: 1712129869394f1f8eabc4cd26d3ab4c
TriggeredBy: ● borgbackup.timer
       Docs: man:borgbackup
    Process: 78255 ExecStart=/nix/store/khkr1l6395czf0sn79i0kmfp7pvimlm5-unit-script-borgbackup-start/bin/borgbackup-start (code=exited, status=1/FAILURE)
   Main PID: 78255 (code=exited, status=1/FAILURE)
         IP: 16.6K in, 18.8K out
         IO: 24K read, 628K written
   Mem peak: 66.2M
        CPU: 1.887s

Jan 21 11:00:02 revelations systemd[1]: Started borgbackup.
Jan 21 11:00:13 revelations borgbackup-start[78267]: /var/vmail/.config/borg/security/25276a6702fe342e099d0c711d20ff31752131884fd017bf76c0169ba84682b2/nonce: file changed while we backed it up
Jan 21 11:00:14 revelations systemd[1]: borgbackup.service: Main process exited, code=exited, status=1/FAILURE
Jan 21 11:00:14 revelations systemd[1]: borgbackup.service: Failed with result 'exit-code'.
Jan 21 11:00:14 revelations systemd[1]: borgbackup.service: Triggering OnFailure= dependencies.
Jan 21 11:00:14 revelations systemd[1]: borgbackup.service: Consumed 1.887s CPU time, 66.2M memory peak, 24K read from disk, 628K written to disk, 16.6K incoming IP traffic, 18.8K outgoing IP traffic.

This commit fixes it by setting HOME to private /tmp for borg.

Levi Zim (3f806ebf) at 21 Jan 11:49

Levi Zim (3e4908fa) at 21 Jan 11:49

Levi Zim (a5be8f79) at 03 Dec 04:04

I think cutting the commit title at 80 characters is deliberate, as @mle said in !145730 (comment 1808629537)

Levi Zim (90e1509f) at 10 Oct 02:31

Levi Zim (2ba607f4) at 07 Oct 14:43

Levi Zim (3a6bda65) at 07 Oct 14:30

Levi Zim (88bdec22) at 07 Oct 14:18

Levi Zim (77a601f3) at 07 Oct 14:14

Levi Zim (bfe6afda) at 07 Oct 14:09