pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedfailures in pg_restore -- possibly corrupt archive
5+ messages / 3 participants
[nested] [flat]
* failures in pg_restore -- possibly corrupt archive
@ 2014-01-02 22:03 AccessDevelopment TEST <caleb.access@gmail.com>
2014-01-02 22:31 ` Re: failures in pg_restore -- possibly corrupt archive Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 5+ messages in thread
From: AccessDevelopment TEST @ 2014-01-02 22:03 UTC (permalink / raw)
To: pgsql-admin
I am attempting to restore a pg dump file and am getting this error message:
pg_restore: [custom archiver] could not find block ID 229750 in archive
-- possibly corrupt archive
pg_restore: [custom archiver] could not find block ID 228874 in archive
-- possibly corrupt archive
pg_restore: [archiver] worker process failed: exit code 1
The pg_restore command used is:
pg_restore -j 12 -d mydb -h myhost -U username /restore/file.dump
pg_dump was used to created the backup.
I have searched around and have found no information that would lead to a
remedy for a successful restore. We have analyzed the disk for bad blocks
and could find no problem there. There is no additional information
provided than the messages listed above.
Any ideas?
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: failures in pg_restore -- possibly corrupt archive
2014-01-02 22:03 failures in pg_restore -- possibly corrupt archive AccessDevelopment TEST <caleb.access@gmail.com>
@ 2014-01-02 22:31 ` Tom Lane <tgl@sss.pgh.pa.us>
2014-01-02 23:12 ` Re: failures in pg_restore -- possibly corrupt archive Caleb Access <caleb.access@gmail.com>
0 siblings, 1 reply; 5+ messages in thread
From: Tom Lane @ 2014-01-02 22:31 UTC (permalink / raw)
To: AccessDevelopment TEST <caleb.access@gmail.com>; +Cc: pgsql-admin
AccessDevelopment TEST <caleb.access@gmail.com> writes:
> I am attempting to restore a pg dump file and am getting this error message:
> pg_restore: [custom archiver] could not find block ID 229750 in archive
> -- possibly corrupt archive
> pg_restore: [custom archiver] could not find block ID 228874 in archive
> -- possibly corrupt archive
> pg_restore: [archiver] worker process failed: exit code 1
> The pg_restore command used is:
> pg_restore -j 12 -d mydb -h myhost -U username /restore/file.dump
This looks suspiciously like some old complaints about unsupported cases
in parallel restore. Does it work if you omit the -j option? If so,
what versions of pg_dump and pg_restore are you using exactly, and what
did the pg_dump command look like?
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: failures in pg_restore -- possibly corrupt archive
2014-01-02 22:03 failures in pg_restore -- possibly corrupt archive AccessDevelopment TEST <caleb.access@gmail.com>
2014-01-02 22:31 ` Re: failures in pg_restore -- possibly corrupt archive Tom Lane <tgl@sss.pgh.pa.us>
@ 2014-01-02 23:12 ` Caleb Access <caleb.access@gmail.com>
0 siblings, 0 replies; 5+ messages in thread
From: Caleb Access @ 2014-01-02 23:12 UTC (permalink / raw)
To: pgsql-admin
The pg_dump and pg_restore look to be the same version on both boxes (
9.1.8 ).
The pg_dump looks like this:
pg_dump \
--host=myhost \
--port=5432 \
--username=myusername \
--format=c \
--file=backup_file.dump \
mydb
*Additional notes:*
The pg_dump is running on a box with CentOS 6.4 / PostgreSQL 9.1.8
The pg_restore is then executed on a box with CentOS 5.9 / PostgreSQL
9.1.8
The .dump file is 41 GB
A $yum list | grep libpq yields nothing on the CentOS 6.4 box but gives
this on 5.9
*$ yum list | grep libpq*
libpqxx.i386 2.6.8-13.el5
epel
libpqxx.x86_64 2.6.8-13.el5
epel
libpqxx-devel.i386 2.6.8-13.el5
epel
libpqxx-devel.x86_64 2.6.8-13.el5 epel
We have not tried without the -j but will give it a go.
Please let me know if there are any additional thoughts giving the new info
above.
On Thu, Jan 2, 2014 at 3:31 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> AccessDevelopment TEST <caleb.access@gmail.com> writes:
> > I am attempting to restore a pg dump file and am getting this error
> message:
> > pg_restore: [custom archiver] could not find block ID 229750 in archive
> > -- possibly corrupt archive
> > pg_restore: [custom archiver] could not find block ID 228874 in archive
> > -- possibly corrupt archive
> > pg_restore: [archiver] worker process failed: exit code 1
>
> > The pg_restore command used is:
> > pg_restore -j 12 -d mydb -h myhost -U username /restore/file.dump
>
> This looks suspiciously like some old complaints about unsupported cases
> in parallel restore. Does it work if you omit the -j option? If so,
> what versions of pg_dump and pg_restore are you using exactly, and what
> did the pg_dump command look like?
>
> regards, tom lane
>
^ permalink raw reply [nested|flat] 5+ messages in thread
* failures in pg_restore -- possibly corrupt archive
@ 2014-01-02 22:55 Caleb Access <caleb.access@gmail.com>
2014-01-02 23:08 ` Re: failures in pg_restore -- possibly corrupt archive Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 5+ messages in thread
From: Caleb Access @ 2014-01-02 22:55 UTC (permalink / raw)
To: pgsql-admin
The pg_dump and pg_restore look to be the same version on both boxes (
9.1.8 ).
The pg_dump looks like this:
pg_dump \
--host=myhost \
--port=5432 \
--username=myusername \
--format=c \
--file=backup_file.dump \
mydb
*Additional notes:*
The pg_dump is running on a box with CentOS 6.4 / PostgreSQL 9.1.8
The pg_restore is then executed on a box with CentOS 5.9 / PostgreSQL
9.1.8
The .dump file is 41 GB
A $yum list | grep libpq yields nothing on the CentOS 6.4 box but gives
this on 5.9
*$ yum list | grep libpq*
libpqxx.i386 2.6.8-13.el5
epel
libpqxx.x86_64 2.6.8-13.el5
epel
libpqxx-devel.i386 2.6.8-13.el5
epel
libpqxx-devel.x86_64 2.6.8-13.el5 epel
We have not tried without the -j but will give it a go.
Please let me know if there are any additional thoughts giving the new info
above.
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: failures in pg_restore -- possibly corrupt archive
2014-01-02 22:55 failures in pg_restore -- possibly corrupt archive Caleb Access <caleb.access@gmail.com>
@ 2014-01-02 23:08 ` Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 5+ messages in thread
From: Tom Lane @ 2014-01-02 23:08 UTC (permalink / raw)
To: Caleb Access <caleb.access@gmail.com>; +Cc: pgsql-admin
Caleb Access <caleb.access@gmail.com> writes:
> The pg_dump and pg_restore look to be the same version on both boxes (
> 9.1.8 ).
Hm, the bug fixes I was thinking of are all older than that, so if it's
a pg_dump or pg_restore bug then it's something previously unreported.
It'd likely be useful to try running pg_restore with -v to track what
it's doing.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2014-01-02 23:12 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2014-01-02 22:03 failures in pg_restore -- possibly corrupt archive AccessDevelopment TEST <caleb.access@gmail.com>
2014-01-02 22:31 ` Tom Lane <tgl@sss.pgh.pa.us>
2014-01-02 23:12 ` Caleb Access <caleb.access@gmail.com>
2014-01-02 22:55 failures in pg_restore -- possibly corrupt archive Caleb Access <caleb.access@gmail.com>
2014-01-02 23:08 ` Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox