From: | Thom Brown <thom(at)linux(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bosco Rama <postgres(at)boscorama(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Unhelpful initdb error message |
Date: | 2012-03-06 18:51:31 |
Message-ID: | CAA-aLv4WcLZoAam3-jh2=FXW2Nmkg=OwmCCAdkSNSwKEvizjsA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 6 March 2012 18:20, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Bosco Rama <postgres(at)boscorama(dot)com> writes:
>> Thom Brown wrote:
>>> I've done that a couple times, but no effect. I think Tom's point
>>> about a filesystem bug is probably right.
>
>> Have you rebooted since this started? There may be a process that is
>> holding the pid file 'deleted but present' until the process terminates.
>
> Even if something is holding the file open, that wouldn't prevent unlink
> from removing the directory entry for it; or even if we were talking
> about a badly-designed filesystem that failed to follow standard Unix
> semantics, that wouldn't explain why the directory entry is apparently
> visible to some operations but not others.
>
> Still, I agree with your point: Thom should reboot and see if the
> misbehavior is still there, because that would be useful info for his
> bug report.
After a reboot, initdb completes successfully. I don't think it
performed an fsck of any kind as I don't see it in the logs.
--
Thom
From | Date | Subject | |
---|---|---|---|
Next Message | dennis jenkins | 2012-03-06 18:51:47 | Re: Unhelpful initdb error message |
Previous Message | Raymond O'Donnell | 2012-03-06 18:25:34 | Re: Adding a lot of tables |