Re: [GENERAL] Re: could not create lock file postmaster.pid: No such file or directory, but file does exist
Rob Goethals / SNP writes: > When it is trying to startup again this is the logfile output: > ... > 2014-02-15 00:50:05 CET PANIC: could not create file > "pg_xlog/xlogtemp.5390": Input/output error The above PANIC is the reason for the abort that happens immediately thereafter. On local storage I'd think this meant disk hardware problems, but since you say you've got the database on an NTFS volume, what it more likely means is that there's a bug in the kernel's NTFS support. Anyway, it's fruitless to try to get Postgres going again until you have a stable filesystem underneath it. Generally speaking, longtime Postgres users are very suspicious of running Postgres atop any kind of networked filesystem. We find that network filesystems are invariably less stable than local ones. NTFS seems likely to be a particularly unfortunate choice from this standpoint, as you get to benefit from Windows' bugs along with Linux's. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Re: could not create lock file postmaster.pid: No such file or directory, but file does exist
On 17 February 2014 14:42, Rob Goethals / SNP wrote: > 2014-02-15 00:49:04 CET LOG: WAL writer process (PID 1127) was terminated > by signal 6: Aborted Signal 6 is usually caused by hardware issues. Then again, you also say: >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. That will cause problems as well. SMBFS does not support all the necessary file flags, locks and such that the database needs to operate on those files in a safe way. That's probably worse than running with sciss... ehr... fsync=off Alban Hertroys. -- If you can't see the forest for the trees, Cut the trees and you'll see there is no forest. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
