Error in Elasticsearch master pod that FileSystemException: /data/log: Input/output error

I found the below error logs in Elasticsearch master pod logs-

Caused by: java.lang.IllegalStateException: Unable to access 'path.logs' (/data/log)
        at org.elasticsearch.bootstrap.FilePermissionUtils.addDirectoryPath( ~[elasticsearch-7.8.0.jar:7.8.0]
        at org.elasticsearch.bootstrap.Security.addFilePermissions( ~[elasticsearch-7.8.0.jar:7.8.0]
        at org.elasticsearch.bootstrap.Security.createPermissions( ~[elasticsearch-7.8.0.jar:7.8.0]
        at org.elasticsearch.bootstrap.Security.configure( ~[elasticsearch-7.8.0.jar:7.8.0]
        at org.elasticsearch.bootstrap.Bootstrap.setup( ~[elasticsearch-7.8.0.jar:7.8.0]
        at org.elasticsearch.bootstrap.Bootstrap.init( ~[elasticsearch-7.8.0.jar:7.8.0]
        at org.elasticsearch.bootstrap.Elasticsearch.init( ~[elasticsearch-7.8.0.jar:7.8.0]
        ... 6 more
Caused by: java.nio.file.FileSystemException: /data/log: Input/output error

ES version deployed : 7.8.0
when login to master pod & check

[elasticsearch@elasticsearch-master-1 ~]$ ls /data/ -ld
drwxrwsr-x. 5 root elasticsearch 4096 Mar 24 21:18 /data/
[elasticsearch@elasticsearch-master-1 ~]$ ls /data/log -ld
drwxrwsr-x. 2 elasticsearch elasticsearch 4096 Mar 24 21:18 /data/log

Could you please help to find the cause for this issue?

is there update for this issue? could someone help in debug?

This means the operating system returned EIO from some kind of IO operation, which indicates a fundamental problem in your storage. You've deleted the bit of the stack trace that says what operation failed, but that's not normally very important anyway. Maybe check dmesg to see if there are any kernel logs indicating storage problems.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.