Failed to list content of shard directory – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.4-7.7

Briefly, this error occurs when Elasticsearch is unable to access or read the shard directory. This could be due to insufficient permissions, disk space issues, or a corrupted shard. To resolve this issue, you can try the following: 1) Check and adjust the permissions of the shard directory. 2) Free up disk space if it’s running low. 3) If the shard is corrupted, consider deleting it and allow Elasticsearch to recreate it from a replica. Always ensure to back up your data before making any changes.

This guide will help you check for common problems that cause the log ” Failed to list content of shard directory ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: blobstore, shard, repositories.

Log Context

Log “Failed to list content of shard directory” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 private static Set getShardBlobs(final ShardId snapshotShardId; final BlobContainer shardContainer) {
 final Set blobs;
 try {
 blobs = shardContainer.listBlobs().keySet();
 } catch (IOException e) {
 throw new IndexShardSnapshotException(snapshotShardId; "Failed to list content of shard directory"; e);
 return blobs;
 }  // Unused blobs are all previous index-; data- and meta-blobs and that are not referenced by the new index- as well as all


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?