From: | Thom Brown <thom(at)linux(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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:00:17 |
Message-ID: | CAA-aLv7TXQ4qyNw8iw22Bs40USBbo=tKNdsJGQPtpn8xCy8+ug@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 6 March 2012 17:53, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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).
You may well be right. There appear to be dark forces at work here:
thom(at)swift:~/Development/data$ touch postmaster.pid
thom(at)swift:~/Development/data$ ls -l
total 0
thom(at)swift:~/Development/data$ touch file.txt
thom(at)swift:~/Development/data$ ls -l
total 8
-rw-rw-r-- 1 thom thom 0 2012-03-06 17:59 file.txt
--
Thom
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2012-03-06 18:01:26 | Re: Unhelpful initdb error message |
Previous Message | Adrian Klaver | 2012-03-06 17:58:41 | Re: Unhelpful initdb error message |