Re: PANIC: could not flush dirty data: Operation not permitted power8, Redhat Centos

From: zedaardv(at)gmail(dot)com
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
Subject: Re: PANIC: could not flush dirty data: Operation not permitted power8, Redhat Centos
Date: 2019-04-15 07:57:43
Message-ID: EE793B78-F3FD-4377-8EE7-71DDA7555648@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

sent by smoke signals at great danger to my self.

> On 12 Apr 2019, at 23:16, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
>
>> On Sat, Apr 13, 2019 at 7:23 AM Andres Freund <andres(at)anarazel(dot)de> wrote:
>>> On 2019-04-12 20:04:00 +0200, reiner peterke wrote:
>>> We build Postgres on Power and x86 With the latest Postgres 11 release (11.2) we get error on
>>> power8 ppc64le (Redhat and CentOS). No error on SUSE on power8
>
> Huh, I wonder what is different. I don't see this on EDB's CentOS
> 7.1 POWER8 system with an XFS filesystem. I ran it under strace -f
> and saw this:
>
> [pid 51614] sync_file_range2(0x19, 0x2, 0x8000, 0x2000, 0x2, 0x8) = 0
>
>>> 2019-04-09 12:30:10 UTC pid:203 xid:0 ip: LOG: listening on IPv4 address "0.0.0.0", port 5432
>>> 2019-04-09 12:30:10 UTC pid:203 xid:0 ip: LOG: listening on IPv6 address "::", port 5432
>>> 2019-04-09 12:30:10 UTC pid:203 xid:0 ip: LOG: listening on Unix socket "/tmp/.s.PGSQL.5432"
>>> 2019-04-09 12:30:10 UTC pid:204 xid:0 ip: LOG: database system was shut down at 2019-04-09 12:27:09 UTC
>>> 2019-04-09 12:30:10 UTC pid:203 xid:0 ip: LOG: database system is ready to accept connections
>>> 2019-04-09 12:31:46 UTC pid:203 xid:0 ip: LOG: received SIGHUP, reloading configuration files
>>> 2019-04-09 12:35:10 UTC pid:205 xid:0 ip: PANIC: could not flush dirty data: Operation not permitted
>>> 2019-04-09 12:35:10 UTC pid:203 xid:0 ip: LOG: checkpointer process (PID 205) was terminated by signal 6: Aborted
>>
>> Any chance you can strace this? Because I don't understand how you'd get
>> a permission error here.
>
> Me neither. I hacked my tree so that it would use the msync() version
> instead of the sync_file_range() version but that worked too.
>
> --
> Thomas Munro
> https://enterprisedb.com

I forgot to mention that this is happening in a docker container.
I want to test it on a VM to see if it is container related. I am sick at the moment so i’m unable to do the test at the moment.

Reiner

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2019-04-15 08:05:16 Re: hyrax vs. RelationBuildPartitionDesc
Previous Message Peter Eisentraut 2019-04-15 07:37:27 Re: cache lookup failed for collation 0