FYI: I tried setting the md5 field to '' in the whole table but that didn't fix the pg_dump issue. In the end I decided to drop the database and revert to my last successful backup. I'm now still reading in all tapes to reconstruct the latest database state.
Thanks for the help anyway.
Nico
On Mon, May 25, 2020 at 4:20 PM Adrian Klaver <adrian.klaver@xxxxxxxxxxx> wrote:
On 5/24/20 10:30 PM, Nico De Ranter wrote:
> Unfortunately not. I discovered the issue rather late. The last working
> backup is about 2 months old.
Well first it is entirely possible this is not the only corruption in
the database.
Second you are probably going to have to reach out to the Bacula folks:
https://www.bacula.org/support/
https://sourceforge.net/projects/bacula/lists/bacula-users
I would say the questions to ask them are:
1) Is the md5 required for a file?
2) If so how and over what is calculated?
Then you could experiment with trying to update the md5 field with new
data.
> >
> >
> >
> > Following up on the max(bigint), I tried
> >
> > SELECT md5 FROM public.file where fileid >2087994666;
> >
> > and got
> >
> > ERROR: compressed data is corrupted
> >
> > So it does look like those entries are killing it. Now for the
> > million-dollar question: how do I get them out?
>
> Do you have recent previous backup?
>
> >
> > Nico
> >
> > --
> >
> > Nico De Ranter
> >
> > Operations Engineer
> >
>
>
>
> --
> Adrian Klaver
> adrian.klaver@xxxxxxxxxxx <mailto:adrian.klaver@xxxxxxxxxxx>
>
>
>
> --
>
> Nico De Ranter
>
> Operations Engineer
>
--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx
Nico De Ranter
Operations Engineer
T. +32 16 38 72 10
eSATURNUS | T. +32 16 40 12 82 |
For Service & Support :
Support Line Belgium: +32 2 2009897
Support Line International: +44 12 56 68 38 78
Or via email : medical.services.eu@xxxxxxxx
