| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thom Brown <thom(at)linux(dot)com> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Unhelpful initdb error message |
| Date: | 2012-03-06 17:53:52 |
| Message-ID: | 2142.1331056432@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Thom Brown <thom(at)linux(dot)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).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2012-03-06 17:58:41 | Re: Unhelpful initdb error message |
| Previous Message | Thom Brown | 2012-03-06 17:51:54 | Re: Unhelpful initdb error message |