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

2019-08-19 Thread Thomas Munro
On Mon, Aug 19, 2019 at 7:32 AM Thomas Munro wrote: > On Wed, Apr 17, 2019 at 1:04 PM Thomas Munro wrote: > > On Mon, Apr 15, 2019 at 7:57 PM wrote: > > > I forgot to mention that this is happening in a docker container. > > > > Huh, so there may be some configuration of Linux container that can

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

2019-08-18 Thread Thomas Munro
On Wed, Apr 17, 2019 at 1:04 PM Thomas Munro wrote: > On Mon, Apr 15, 2019 at 7:57 PM wrote: > > I forgot to mention that this is happening in a docker container. > > Huh, so there may be some configuration of Linux container that can > fail here with EPERM, even though that error that does not a

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

2019-04-16 Thread Thomas Munro
On Mon, Apr 15, 2019 at 7:57 PM wrote: > I forgot to mention that this is happening in a docker container. Huh, so there may be some configuration of Linux container that can fail here with EPERM, even though that error that does not appear in the man page, and doesn't make much intuitive sense.

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

2019-04-15 Thread Justin Pryzby
On Fri, Apr 12, 2019 at 08:04:00PM +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 > > No error on x86_64 (RH, Centos and SUSE) So there's an error on

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

2019-04-15 Thread zedaardv
sent by smoke signals at great danger to my self. > On 12 Apr 2019, at 23:16, Thomas Munro wrote: > >> On Sat, Apr 13, 2019 at 7:23 AM Andres Freund 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 >>>

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

2019-04-12 Thread Thomas Munro
On Sat, Apr 13, 2019 at 7:23 AM Andres Freund 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

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

2019-04-12 Thread Tom Lane
Andres Freund writes: > 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 > Any chance you can strace this? Because I don't und

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

2019-04-12 Thread Andres Freund
Hi, 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 > 2019-04-09 12:30:10 UTC pid:203 xid:0 ip: LOG: listening on IPv4 addres

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

2019-04-12 Thread reiner peterke
Hi All, 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 No error on x86_64 (RH, Centos and SUSE) from the log file 2019-04-09 12:30:10 UTC pid:203 xid:0 ip: LOG: listening on IPv4 a