| 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 18:10:07 |
| Message-ID: | 2520.1331057407@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Thom Brown <thom(at)linux(dot)com> writes:
> On 6 March 2012 18:01, Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> wrote:
>> A thought, what if you do rm -rf * in the data directory?
> I've done that a couple times, but no effect. I think Tom's point
> about a filesystem bug is probably right.
Yeah, given your "touch" experiment I think that you have more than
enough ammunition to file a kernel bug. Apparently, the directory
contents are corrupted in such a way that a file named "postmaster.pid"
can be created but it's invisible to some (perhaps not all) operations.
In some of the more complex directory data structures I could believe
that this result is filename-sensitive (think corrupted hashtable...)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bosco Rama | 2012-03-06 18:12:50 | Re: Unhelpful initdb error message |
| Previous Message | Magnus Hagander | 2012-03-06 18:08:03 | Re: Unhelpful initdb error message |