[Borgbackup] Reboot with no warning when check/repair

[Bzzzz]

On Sun, 17 Jan 2021 08:58:31 -0500
Neal Becker <ndbecker2 at gmail.com> wrote:

Rahhh, sorry for the PM @#\! ML new behavior :(

> Perhaps you can temporarily add file swap

Ziziz what the raspbian OS does natively, however, with only a few
daemons and several Erlang VMs running on it, I never even reached half
of the memory (4 GB) - so I lowered swapiness to 3, removed the 1 GB
swap file and, at this time, never had a problem until BB triggered one.

> On Sun, Jan 17, 2021, 8:33 AM Bzzzz <lazyvirus at gmx.com> wrote:
>
> > On Sun, 17 Jan 2021 13:50:39 +0100
> > Thomas Waldmann <tw at waldmann-edv.de> wrote:
> >
> > > >> borgbackup     1.1.9-2+deb10u1 armhf
> > > >> (distro package)
> > >
> > > Can you use a more recent borg?
> > >
> > > Maybe one from backports or the arm fat binary (see github issues /
> > > borg community resources)?
> > >
> > > 1.1.15 would be good. Then try to reproduce.
> >
> > Nope, I downloaded the 1.1.15-1 pkg, but its installation failed
> > because of Python3 version :
> >
> > Preparing to unpack .../borgbackup_1.1.15-1_armhf.deb ...
> > Unpacking borgbackup (1.1.15-1) over (1.1.9-2+deb10u1) ...
> > dpkg: dependency problems prevent configuration of borgbackup:
> >  borgbackup depends on python3 (>= 3.9~); however:
> >   Version of python3 on system is 3.7.3-1.
> >  borgbackup depends on libgcc-s1 (>= 3.5); however:
> >   Package libgcc-s1 is not installed.
> >
> > Ah, pip install borgbackup agreed to set 1.1.15 up, testing now.
> >
> > > I've recently fixed some memory leaks (not specifically in borg
> > > check though, iirc).
> > >
> > > >> borg check --verify --repair --progress --show-rc /BORG/
> > > >> (/BORG being a NFS mount).
> > >
> > > borg does not have a "--verify" parameter. So please give the full
> > > command exactly as you used it.
> >
> > Strange, I don't know where I pick that, corrected to --verify-data
> >
> > > In case you actually have used --verify-data, you could try to
> > > reproduce without that.
> > >
> > > Also, try to specifically watch the memory consumption of borg to
> > > see if it really is the borg process. A reboot is a bit strange,
> > > isn't the OOM killer usually just shooting the biggest process?
> >
> > I have to dig into the watchdog configuration possibilities (a reboot
> > being not particularly a problem at this time, but will be later).
> >
> > > If you do not have swap, maybe add some.
> >
> > I don't have one, due to a SSD.
> > _______________________________________________
> > Borgbackup mailing list
> > Borgbackup at python.org
> > https://mail.python.org/mailman/listinfo/borgbackup
> >