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

On Sat, Apr 13, 2019 at 7:23 AM Andres Freund <andres@anarazel.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