Can t mark store as corrupted – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-6.8

Briefly, this error occurs when Elasticsearch fails to mark a data store as corrupted due to insufficient permissions or disk space issues. To resolve this, you can try the following: 1) Check and adjust the permissions of the Elasticsearch data directory to ensure it has write access. 2) Free up disk space if it’s running low. 3) Check the health of your hard drive, as physical damage could also cause this error. 4) If the error persists, consider moving your data to a new node or data store.

This guide will help you check for common problems that cause the log ” Can’t mark store as corrupted ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index.

Log Context

Log “Can’t mark store as corrupted” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                BytesRef ref = bytes.toBytesRef();
                output.writeBytes(ref.bytes; ref.offset; ref.length);
            } catch (IOException ex) {
                logger.warn("Can't mark store as corrupted"; ex);


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?