Thread: BUG #15221: Could not open file "pg_subtrans/0013"

The following bug has been logged on the website:

Bug reference:      15221
Logged by:          lily liang
Email address:      joanaliang_05@126.com
PostgreSQL version: 10.2
Operating system:   Redhat
Description:

hi,

we're using postgresql 10.2, postgresql is deployed in a docker image. it
works well for some time. but one day we met errors when we test with load.
In logs, we found below errors:

2018-05-28T10:08:38.487336192Z 2018-05-28 10:08:38.487 UTC [110] ERROR:
could not access status of transaction 0
2018-05-28T10:08:38.487348231Z 2018-05-28 10:08:38.487 UTC [110] DETAIL:
Could not open file "pg_subtrans/0013": Invalid argument.
2018-05-28T10:08:38.509453008Z 2018-05-28 10:08:38.509 UTC [110] STATEMENT:
INSERT INTO schemas VALUES ('abc1', '{"schema": {"$schema":
"http://json-schema.org/schema#", "required": ["color"], "type": "object",
"properties": {"color": {"type": "string"}}}, "format": "json", "title":
"abc schema"}')


after we restart and re-run the test, the error disppears. 

the database data is mounted and stored to a NFS folder.

Cheers and thanks.

=?utf-8?q?PG_Bug_reporting_form?= <noreply@postgresql.org> writes:
> 2018-05-28T10:08:38.487348231Z 2018-05-28 10:08:38.487 UTC [110] DETAIL: 
> Could not open file "pg_subtrans/0013": Invalid argument.

EINVAL on a file open is pretty uncommon ...

> the database data is mounted and stored to a NFS folder.

... but I've heard of it happening with unstable NFS setups.

You might check for NFS version compatibility, firewalls blocking
some of the ports NFS uses, etc.

But really my advice would be "don't access your database over NFS".
It's just not reliable enough.

            regards, tom lane

On 2018-May-31, PG Bug reporting form wrote:

> we're using postgresql 10.2, postgresql is deployed in a docker image. it
> works well for some time. but one day we met errors when we test with load.
> In logs, we found below errors:
> 
> 2018-05-28T10:08:38.487336192Z 2018-05-28 10:08:38.487 UTC [110] ERROR: 
> could not access status of transaction 0
> 2018-05-28T10:08:38.487348231Z 2018-05-28 10:08:38.487 UTC [110] DETAIL: 
> Could not open file "pg_subtrans/0013": Invalid argument.

While reviewing this bug report a few days ago I noticed that there was
one place that would report "could not open file" on a failure to
lseek(), because a wrong enum value used as function indicator was set.
It could not possibly be involved in this report, because that code is
only used by multixact.c and commit_ts.c in branch 10.  Nevertheless, I
applied a patch to fix that.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services