From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
---|---|
To: | "Rob Goethals / SNP *EXTERN*" <Rob(dot)Goethals(at)snp(dot)nl> |
Cc: | "'pgsql-general(at)postgresql(dot)org'" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: could not create lock file postmaster.pid: No such file or directory, but file does exist |
Date: | 2014-02-17 15:20:24 |
Message-ID: | A737B7A37273E048B164557ADEF4A58B17CA7F12@ntex2010i.host.magwien.gv.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-general |
Rob Goethals wrote:
> OK, clear. I hereby send this reply also to the list.
Cool.
>> Interesting.
>> How did you get PostgreSQL into this state? Did you set fsync=off or similar?
>> Which storage did you put pg_xlog on?
> 2014-02-15 00:49:04 CET LOG: WAL writer process (PID 1127) was terminated by signal 6: Aborted
Ouch.
> Furthermore I checked my conf-file and my fsync is indeed set to off.
Well, that is one reason why crash recovery is not working.
> I mounted a directory on a NTFS network-disk (because of the available size and considering the amount
> of OSM-data is pretty big). This is where I put all my database data, so also the pg_xlog.
Double ouch.
CIFS is not a supported file system.
At least that explains your problems.
Try with a local file system or NFS with hard foreground mount.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Rob Goethals / SNP | 2014-02-17 15:42:17 | Re: could not create lock file postmaster.pid: No such file or directory, but file does exist |
Previous Message | Tom Lane | 2014-02-17 15:09:38 | Re: Re: could not create lock file postmaster.pid: No such file or directory, but file does exist |
From | Date | Subject | |
---|---|---|---|
Next Message | Rémi Cura | 2014-02-17 15:25:05 | Re: Toast and slice of toast |
Previous Message | Tom Lane | 2014-02-17 15:09:38 | Re: Re: could not create lock file postmaster.pid: No such file or directory, but file does exist |