Failed to list directory – some of files might not be deleted – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.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 Elasticsearch operation.

Briefly, this error occurs when Elasticsearch tries to delete files but fails because it cannot list the directory. This could be due to insufficient permissions, a locked file, or a file system issue. To resolve this, you can manually delete the files if they are no longer needed. If the issue persists, check the file permissions and ensure Elasticsearch has the necessary access. Also, verify that no other processes are locking the files. Lastly, check the health of your file system to rule out any underlying issues.

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 ” [{}] [{}] failed to list directory – some of files might not be deleted ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repositories, blobstore.

Log Context

Log “[{}] [{}] failed to list directory – some of files might not be deleted” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                } catch (IOException e) {
                    logger.warn("[{}] [{}] failed to delete file [{}] during snapshot cleanup"; shardId; snapshotId; storeFile);
        } catch (IOException e) {
            logger.warn("[{}] [{}] failed to list directory - some of files might not be deleted"; shardId; snapshotId);

     * Restores given list of {@link BlobStoreIndexShardSnapshot.FileInfo} to the given {@link Store}.


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?