Re: Unhelpful initdb error message - Mailing list pgsql-general

From Adrian Klaver
Subject Re: Unhelpful initdb error message
Date
Msg-id 201203061001.27178.adrian.klaver@gmail.com
Whole thread Raw
In response to Re: Unhelpful initdb error message  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Unhelpful initdb error message  (Thom Brown <thom@linux.com>)
List pgsql-general
On Tuesday, March 06, 2012 9:53:52 am Tom Lane wrote:
> Thom Brown <thom@linux.com> writes:
> > /home/thom/Development/data was causing problems so:
> >
> > mv data databroken
> > mkdir data
> > initdb
> >
> > ... working fine again.  I then used the postmaster.pid from this when
> > started up.  But if I do:
> >
> > pg_ctl stop
> > rm -rf data
> > mv databroken data
> > initdb
> >
> > ... error messages appear again.
>
> Okay, so the question becomes: what is different between databroken and
> a freshly mkdir'd empty directory?  If there is no visible difference in
> contents, ownership, or permissions, then it seems like this is evidence
> of a filesystem bug (ie, apparently empty directory acts nonempty for
> some operations).

A thought, what if you do rm -rf * in the data directory?

>
>             regards, tom lane

--
Adrian Klaver
adrian.klaver@gmail.com

pgsql-general by date:

Previous
From: Thom Brown
Date:
Subject: Re: Unhelpful initdb error message
Next
From: Gavin Flower
Date:
Subject: Re: what Linux to run