[Borgbackup] Reboot with no warning when check/repair

[Bzzzz]

On Sat, 16 Jan 2021 15:48:41 +0100
Bzzzz <lazyvirus at gmx.com> wrote:

There's something new and it is bad.

I enabled the intrinsic watchdog and restarted the procedure, leaving the
machine display always on to survey what was happening.

In fact, it breaks when into the second phase (verifying data) @~45% and
the watchdog had the time to send me an e-mail, saying it was rebooting
because the system cannot allocate memory (armhf being a 32-bit OS,
this means borg is claiming more than 3 GB of RAM :/)

Sooo, the question has change to : is there a way to limit the memory
quantity borg want when in check/repair mode ?

Jean-Yves

> borgbackup     1.1.9-2+deb10u1 armhf
> (distro package)
> ====================================
>
> Hi list,
>
> As of each 4 months, I launch a check/repair on all machines :
> borg check --verify --repair --progress --show-rc /BORG/
> (/BORG being a NFS mount).
>
> On my recent raspberry pi 4 8GB, I've got a weird behavior, after
> ~5-6 h (still in the checking segment phase), it reboots without any
> warning and not a trace in log files :/
>
> @33.3% of checking segments, memory isn't very much impacted :
> root      3374  0.9  0.9  90644 78896 pts/6    D+   14:01
> 0:55          |                   \_ /usr/bin/python3 /usr/bin/borg
> check --verify --repair --progress --show-rc /BORG/
>
> Two attempts have lead to the same reboot - at this point, the only
> option I see would be to wipe the rpi4 repo and recreate it from
> scratch.
>
> What could trigger such an event ?
> And is there a way to avoid that ?
>
> Jean-Yves
> _______________________________________________
> Borgbackup mailing list
> Borgbackup at python.org
> https://mail.python.org/mailman/listinfo/borgbackup