On Sat, 2022-05-21 at 12:32 +0100, Patrick O'Callaghan wrote:
> On Fri, 2022-05-20 at 18:20 -0700, Gordon Messmer wrote:
> > On 5/20/22 14:15, Patrick O'Callaghan wrote:
> > > Thanks, but it's a desktop and the issue appears to be related to
> > > the
> > > latest version of Borg. The check errors
On Fri, 2022-05-20 at 18:20 -0700, Gordon Messmer wrote:
> On 5/20/22 14:15, Patrick O'Callaghan wrote:
> > Thanks, but it's a desktop and the issue appears to be related to
> > the
> > latest version of Borg. The check errors happen across all of my
> > existing backups, not just one.
>
>
> As a
On 5/20/22 14:15, Patrick O'Callaghan wrote:
Thanks, but it's a desktop and the issue appears to be related to the
latest version of Borg. The check errors happen across all of my
existing backups, not just one.
As a result of deduplication, it's expected that all (or most) of your
backups wi
On Fri, 2022-05-20 at 12:12 -0700, Gordon Messmer wrote:
> On 5/16/22 08:45, Patrick O'Callaghan wrote:
> > I updated to F36 a few days ago and everything seemed to go
> > smoothly
> > until I noticed my regular nightly backups were failing. I use
> > Borgbackup and the configuration has been stabl
On 5/16/22 08:45, Patrick O'Callaghan wrote:
I updated to F36 a few days ago and everything seemed to go smoothly
until I noticed my regular nightly backups were failing. I use
Borgbackup and the configuration has been stable for a long time with
no problems. The actual backup does seem to succee
On Tue, 2022-05-17 at 13:11 +0200, Markus Schönhaber wrote:
> 17.05.22, 11:48 +0200, Patrick O'Callaghan:
>
> > On Mon, 2022-05-16 at 16:08 -0600, James Szinger wrote:
>
> > > Also, my systems are using borgbackup-1.1.17-1.fc35 and
> > > borgbackup-1.2.0-1.fc36. How did you get 1.2.0 on F35?
> >
17.05.22, 11:48 +0200, Patrick O'Callaghan:
On Mon, 2022-05-16 at 16:08 -0600, James Szinger wrote:
Also, my systems are using borgbackup-1.1.17-1.fc35 and
borgbackup-1.2.0-1.fc36. How did you get 1.2.0 on F35?
I simply updated with dnf and there it was. Didn´t do anything special.
1.1x wa
On Mon, 2022-05-16 at 16:08 -0600, James Szinger wrote:
> On Mon, 16 May 2022 20:56:10 +0100
> Patrick O'Callaghan wrote:
>
> > On Mon, 2022-05-16 at 18:20 +0200, Markus Schönhaber wrote:
> > > 16.05.22, 17:45 +0200, Patrick O'Callaghan:
> > >
> > > > I updated to F36 a few days ago and everyt
On Mon, 16 May 2022 20:56:10 +0100
Patrick O'Callaghan wrote:
> On Mon, 2022-05-16 at 18:20 +0200, Markus Schönhaber wrote:
> > 16.05.22, 17:45 +0200, Patrick O'Callaghan:
> >
> > > I updated to F36 a few days ago and everything seemed to go
> > > smoothly
> > > until I noticed my regular nigh
On Mon, 2022-05-16 at 18:20 +0200, Markus Schönhaber wrote:
> 16.05.22, 17:45 +0200, Patrick O'Callaghan:
>
> > I updated to F36 a few days ago and everything seemed to go
> > smoothly
> > until I noticed my regular nightly backups were failing. I use
> > Borgbackup and the configuration has been
16.05.22, 17:45 +0200, Patrick O'Callaghan:
I updated to F36 a few days ago and everything seemed to go smoothly
until I noticed my regular nightly backups were failing. I use
Borgbackup and the configuration has been stable for a long time with
no problems. The actual backup does seem to succee
I updated to F36 a few days ago and everything seemed to go smoothly
until I noticed my regular nightly backups were failing. I use
Borgbackup and the configuration has been stable for a long time with
no problems. The actual backup does seem to succeed, but Borg runs a
post-backup repository check
12 matches
Mail list logo
