| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | m(dot)hewitt(at)computer(dot)org, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Postmaster will not restart |
| Date: | 2001-07-30 21:10:10 |
| Message-ID: | 22112.996527410@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
pgsql-bugs(at)postgresql(dot)org writes:
> As far as I know, the postmaster terminated correctly, but now
> when I restart it I have:
> DEBUG: database system was shut down at 2001-07-30 21:17:17 BST
> DEBUG: CheckPoint record at (0, 214140268)
> DEBUG: Redo record at (0, 214140268); Undo record at (0, 0); Shutdown TRUE
> DEBUG: NextTransactionId: 221440; NextOid: 617393
> FATAL 2: ZeroFill(/work/database/postgres/pg_xlog/xlogtemp.449)
> failed: No such file or directory
Looks to me like you have insufficient free space on your disk --- the
code is trying to create another 16-MB WAL segment, and is failing,
no doubt for lack of free space. (Yes, the quoted kernel error message
is incorrect ... that problem is patched in current sources.)
If you do have more than 16MB free on your WAL disk, then there's
another problem...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joseph Shraibman | 2001-07-30 21:22:47 | Re: HELP! BUG? pg_dump mucks up grant/revoke |
| Previous Message | pgsql-bugs | 2001-07-30 20:47:53 | Postmaster will not restart |