| From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | "digoal(at)126(dot)com" <digoal(at)126(dot)com>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #10013: PostgreSQL 9.4 initdb FATAL: could not write to file "pg_xlog/xlogtemp.3590": No space left on devi |
| Date: | 2014-04-16 11:11:22 |
| Message-ID: | 534E655A.8030200@vmware.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 04/16/2014 01:59 PM, Andres Freund wrote:
> On 2014-04-16 13:50:35 +0300, Heikki Linnakangas wrote:
>> On 04/16/2014 11:20 AM, digoal(at)126(dot)com wrote:
>>> HI,
>>> I can reproduce this.
>>
>> Ok. Can you try with the attached patch applied, please?
>
> Perhaps this should also support partial writes, akin to
> 79ce29c734c6a652b2f7193bda537cff0c8eb8c1? I don't find it all that
> unreasonble for the OS to refuse 16MB - or even bigger - writes in some
> scenarios.
The write in XLogFileInit is always 8kB (XLOG_BLCKSZ). But yeah, it
might make sense to retry. Although I wonder why XLogFileInit would be
particularly vulnerable to short writes. I'm afraid if we fix that, next
we'll start seeing failures from other writes, to data files.
But wait for Digoal to run with the extra let's see if this was in fact
a short write. Could also be a quota or similar.
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-04-16 11:16:45 | Re: BUG #10013: PostgreSQL 9.4 initdb FATAL: could not write to file "pg_xlog/xlogtemp.3590": No space left on devi |
| Previous Message | Andres Freund | 2014-04-16 10:59:16 | Re: BUG #10013: PostgreSQL 9.4 initdb FATAL: could not write to file "pg_xlog/xlogtemp.3590": No space left on devi |