Unexpected exception reading filesystem info – How to solve this OpenSearch error

Opster Team

Aug-23, Version: 1-2.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your OpenSearch operation.

Briefly, this error occurs when OpenSearch encounters an issue while trying to read information from the filesystem. This could be due to a lack of permissions, a corrupted filesystem, or a disk failure. To resolve this issue, you can try the following: 1) Check and correct the permissions of the OpenSearch directories. 2) Run a filesystem check tool to identify and fix any corruption. 3) If it’s a disk failure, replace the faulty disk and restore the data from a backup. Always ensure that your system is regularly backed up to prevent data loss.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” unexpected exception reading filesystem info ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: monitor.

Log Context

Log “unexpected exception reading filesystem info” classname is FsService.java.
We extracted the following from OpenSearch source code for those seeking an in-depth context :

    private static FsInfo stats(FsProbe probe; FsInfo initialValue) {
        try {
            return probe.stats(initialValue);
        } catch (IOException e) {
            logger.debug("unexpected exception reading filesystem info"; e);
            return null;

    private static class FsInfoCache extends SingleObjectCache {


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?

Get expert answers on Elasticsearch/OpenSearch