Re: PostgreSQL 8 install fails (initdb) - Mailing list pgsql-general

From Tom Lane
Subject Re: PostgreSQL 8 install fails (initdb)
Date
Msg-id 29860.1108999662@sss.pgh.pa.us
Whole thread Raw
In response to PostgreSQL 8 install fails (initdb)  (koester@x-itec.de)
Responses Re: PostgreSQL 8 install fails (initdb)  (koester@x-itec.de)
Re: PostgreSQL 8 install fails (initdb)  (koester@x-itec.de)
List pgsql-general
koester@x-itec.de writes:
> I have downloaded release 8.x for installation. Compilation and so on
> works fine (FreeBSD 5.2.1)

> initdb fails with the following informations:

> copying template1 to template0 ... cp: /usr/local/pgsql/data/base/1/16384: Invalid argument
> cp: /usr/local/pgsql/data/base/1/17175: Invalid argument
> cp: /usr/local/pgsql/data/base/1/17180: Invalid argument
> cp: /usr/local/pgsql/data/base/1/17183: Invalid argument
> cp: /usr/local/pgsql/data/base/1/17185: Invalid argument
> ...
> FATAL:  could not initialize database directory
> DETAIL:  Failing system command was: cp -r '/usr/local/pgsql/data/base/1' '/usr/local/pgsql/data/base/17229'
> HINT:  Look in the postmaster's stderr log for more information.
> child process exited with exit code 1
> initdb: removing data directory "/usr/local/pgsql/data"

> Anything I can do?

Complain to some FreeBSD hackers?  This seems like it must be a kernel
bug (or perhaps a bug in cp itself).  I don't think Postgres did
anything wrong.

            regards, tom lane

pgsql-general by date:

Previous
From: Bo Lorentsen
Date:
Subject: Re: Deadlock and FK triggers
Next
From: Bruce Momjian
Date:
Subject: Re: Deadlock and FK triggers