# Unnable to list snapshots in Elasticsearch repository

**URL:** <https://discuss.elastic.co/t/unnable-to-list-snapshots-in-elasticsearch-repository/271425>\
**Category:** Elasticsearch\
**Tags:** snapshot-and-restore\
**Created:** [April 27, 2021, 5:57pm UTC](https://discuss.elastic.co/t/unnable-to-list-snapshots-in-elasticsearch-repository/271425 "2021-04-27T17:57:38Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [April 30, 2021, 8:15am UTC](https://discuss.elastic.co/t/unnable-to-list-snapshots-in-elasticsearch-repository/271425/21 "2021-04-30T08:15:07Z")

</div>

What is the output of:

```auto
GET /
GET /_cat/nodes?v
GET /_cat/health?v

```

This time, do not post screenshots but just the output as you did previously.

Is there any chance that you registered the same repository on multiple clusters using different versions of the cluster?

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [April 30, 2021, 8:23am UTC](https://discuss.elastic.co/t/unnable-to-list-snapshots-in-elasticsearch-repository/271425/22 "2021-04-30T08:23:18Z")

</div>

I think we want to see the stack trace to better understand what exactly is failing:

```auto
curl -X GET "10.0.1.159:9200/_cat/snapshots/temp_elastic_backup?error_trace"

```

---

<div class="post-metadata">

**Author:** ![KA3AXCTAH](https://avatars.discourse-cdn.com/v4/letter/k/919ad9/32.png) [@KA3AXCTAH](https://discuss.elastic.co/u/KA3AXCTAH)\
**Post date:** [April 30, 2021, 9:08am UTC](https://discuss.elastic.co/t/unnable-to-list-snapshots-in-elasticsearch-repository/271425/23 "2021-04-30T09:08:40Z")

</div>

No, version was the same  
here is curls

```auto
curl -X GET "localhost:9200/"
{
  "name" : "loges-prod-15-uv03.",
  "cluster_name" : "elasticsearch",
  "cluster_uuid" : "JQASlHJoQlO737P9hPV6cg",
  "version" : {
    "number" : "7.4.1",
    "build_flavor" : "default",
    "build_type" : "rpm",
    "build_hash" : "fc0eeb6e2c25915d63d871d344e3d0b45ea0ea1e",
    "build_date" : "2019-10-22T17:16:35.176724Z",
    "build_snapshot" : false,
    "lucene_version" : "8.2.0",
    "minimum_wire_compatibility_version" : "6.8.0",
    "minimum_index_compatibility_version" : "6.0.0-beta1"
  },
  "tagline" : "You Know, for Search"
}

```

/cat/nodes

```auto
curl localhost:9200/_cat/nodes
127.0.0.1 24 15 0 0.00 0.01 0.05 dilm * loges-prod-15-uv03.

```

/health/

```auto
curl -X GET "localhost:9200/_cluster/health?wait_for_status=yellow&timeout=50s&pretty"
{
  "cluster_name" : "elasticsearch",
  "status" : "green",
  "timed_out" : false,
  "number_of_nodes" : 1,
  "number_of_data_nodes" : 1,
  "active_primary_shards" : 0,
  "active_shards" : 0,
  "relocating_shards" : 0,
  "initializing_shards" : 0,
  "unassigned_shards" : 0,
  "delayed_unassigned_shards" : 0,
  "number_of_pending_tasks" : 0,
  "number_of_in_flight_fetch" : 0,
  "task_max_waiting_in_queue_millis" : 0,
  "active_shards_percent_as_number" : 100.0
}

```

---

<div class="post-metadata">

**Author:** ![KA3AXCTAH](https://avatars.discourse-cdn.com/v4/letter/k/919ad9/32.png) [@KA3AXCTAH](https://discuss.elastic.co/u/KA3AXCTAH)\
**Post date:** [April 30, 2021, 9:12am UTC](https://discuss.elastic.co/t/unnable-to-list-snapshots-in-elasticsearch-repository/271425/24 "2021-04-30T09:12:49Z")

</div>

Here is output

```
curl -X GET "localhost:9200/_cat/snapshots/temp_elastic_backup?error_trace"

{"error":{"root_cause":[{"type":"parse_exception","reason":"start object expected","stack_trace":"ElasticsearchParseException[start object expected]\n\tat org.elasticsearch.repositories.RepositoryData.snapshotsFromXContent(RepositoryData.java:431)\n\tat org.elasticsearch.repositories.blobstore.BlobStoreRepository.getRepositoryData(BlobStoreRepository.java:790)\n\tat org.elasticsearch.repositories.blobstore.BlobStoreRepository.getRepositoryData(BlobStoreRepository.java:769)\n\tat org.elasticsearch.snapshots.SnapshotsService.getRepositoryData(SnapshotsService.java:157)\n\tat org.elasticsearch.action.admin.cluster.snapshots.get.TransportGetSnapshotsAction.masterOperation(TransportGetSnapshotsAction.java:99)\n\tat org.elasticsearch.action.admin.cluster.snapshots.get.TransportGetSnapshotsAction.masterOperation(TransportGetSnapshotsAction.java:56)\n\tat org.elasticsearch.action.support.master.TransportMasterNodeAction.masterOperation(TransportMasterNodeAction.java:94)\n\tat org.elasticsearch.action.support.master.TransportMasterNodeAction$AsyncSingleAction.lambda$doStart$3(TransportMasterNodeAction.java:165)\n\tat org.elasticsearch.action.ActionRunnable$1.doRun(ActionRunnable.java:45)\n\tat org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:773)\n\tat org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\n\tat java.base/java.lang.Thread.run(Thread.java:830)\n"}],"type":"parse_exception","reason":"start object expected","stack_trace":"ElasticsearchParseException[start object expected]\n\tat org.elasticsearch.repositories.RepositoryData.snapshotsFromXContent(RepositoryData.java:431)\n\tat org.elasticsearch.repositories.blobstore.BlobStoreRepository.getRepositoryData(BlobStoreRepository.java:790)\n\tat org.elasticsearch.repositories.blobstore.BlobStoreRepository.getRepositoryData(BlobStoreRepository.java:769)\n\tat org.elasticsearch.snapshots.SnapshotsService.getRepositoryData(SnapshotsService.java:157)\n\tat org.elasticsearch.action.admin.cluster.snapshots.get.TransportGetSnapshotsAction.masterOperation(TransportGetSnapshotsAction.java:99)\n\tat org.elasticsearch.action.admin.cluster.snapshots.get.TransportGetSnapshotsAction.masterOperation(TransportGetSnapshotsAction.java:56)\n\tat org.elasticsearch.action.support.master.TransportMasterNodeAction.masterOperation(TransportMasterNodeAction.java:94)\n\tat org.elasticsearch.action.support.master.TransportMasterNodeAction$AsyncSingleAction.lambda$doStart$3(TransportMasterNodeAction.java:165)\n\tat org.elasticsearch.action.ActionRunnable$1.doRun(ActionRunnable.java:45)\n\tat org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:773)\n\tat org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\n\tat java.base/java.lang.Thread.run(Thread.java:830)\n"},"status":400}
```

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [April 30, 2021, 9:18am UTC](https://discuss.elastic.co/t/unnable-to-list-snapshots-in-elasticsearch-repository/271425/25 "2021-04-30T09:18:48Z")

</div>

So you have only onde single node for this cluster and absolutely no data in it?

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [April 30, 2021, 9:25am UTC](https://discuss.elastic.co/t/unnable-to-list-snapshots-in-elasticsearch-repository/271425/26 "2021-04-30T09:25:14Z")

</div>

Thanks. What version is this from?

* * *

edit: 7.4.1 it seems, I thought you had upgraded to 7.12.1 but that stack trace doesn't make sense there:

```auto
ElasticsearchParseException[start object expected]
        at org.elasticsearch.repositories.RepositoryData.snapshotsFromXContent(RepositoryData.java:431)
        at org.elasticsearch.repositories.blobstore.BlobStoreRepository.getRepositoryData(BlobStoreRepository.java:790)
        at org.elasticsearch.repositories.blobstore.BlobStoreRepository.getRepositoryData(BlobStoreRepository.java:769)
        at org.elasticsearch.snapshots.SnapshotsService.getRepositoryData(SnapshotsService.java:157)
        at org.elasticsearch.action.admin.cluster.snapshots.get.TransportGetSnapshotsAction.masterOperation(TransportGetSnapshotsAction.java:99)
        at org.elasticsearch.action.admin.cluster.snapshots.get.TransportGetSnapshotsAction.masterOperation(TransportGetSnapshotsAction.java:56)
        at org.elasticsearch.action.support.master.TransportMasterNodeAction.masterOperation(TransportMasterNodeAction.java:94)
        at org.elasticsearch.action.support.master.TransportMasterNodeAction$AsyncSingleAction.lambda$doStart$3(TransportMasterNodeAction.java:165)
        at org.elasticsearch.action.ActionRunnable$1.doRun(ActionRunnable.java:45)
        at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:773)
        at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:830)

```

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [April 30, 2021, 9:31am UTC](https://discuss.elastic.co/t/unnable-to-list-snapshots-in-elasticsearch-repository/271425/27 "2021-04-30T09:31:28Z")

</div>

Your repository contents appear to be corrupted: the top-level metadata file does not contain a JSON object (it's probably empty). There have been many changes in how Elasticsearch interacts with the repository since 7.4 (which is past [EOL](https://www.elastic.co/support/eol)) so I'm not sure if this might be explained by a bug that's since been fixed, or whether it's due to some problem outside of Elasticsearch. I'm pretty sure it's impossible for recent versions to get into this state anyway. I suggest you upgrade to 7.12 and start again with a fresh repository.

---

<div class="post-metadata">

**Author:** ![KA3AXCTAH](https://avatars.discourse-cdn.com/v4/letter/k/919ad9/32.png) [@KA3AXCTAH](https://discuss.elastic.co/u/KA3AXCTAH)\
**Post date:** [April 30, 2021, 9:31am UTC](https://discuss.elastic.co/t/unnable-to-list-snapshots-in-elasticsearch-repository/271425/28 "2021-04-30T09:31:33Z")

</div>

no this fresh vm which connects to the repo

---

<div class="post-metadata">

**Author:** ![KA3AXCTAH](https://avatars.discourse-cdn.com/v4/letter/k/919ad9/32.png) [@KA3AXCTAH](https://discuss.elastic.co/u/KA3AXCTAH)\
**Post date:** [April 30, 2021, 9:32am UTC](https://discuss.elastic.co/t/unnable-to-list-snapshots-in-elasticsearch-repository/271425/29 "2021-04-30T09:32:14Z")

</div>

I can upgrade my node and read my repo again with trace

---

<div class="post-metadata">

**Author:** ![KA3AXCTAH](https://avatars.discourse-cdn.com/v4/letter/k/919ad9/32.png) [@KA3AXCTAH](https://discuss.elastic.co/u/KA3AXCTAH)\
**Post date:** [April 30, 2021, 9:34am UTC](https://discuss.elastic.co/t/unnable-to-list-snapshots-in-elasticsearch-repository/271425/30 "2021-04-30T09:34:46Z")

</div>

and this repository is important to me, because this backup our production system logs, they rotate to NFS share for Archieve format...

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [April 30, 2021, 9:37am UTC](https://discuss.elastic.co/t/unnable-to-list-snapshots-in-elasticsearch-repository/271425/31 "2021-04-30T09:37:34Z")

</div>

Ok, do you have a [repository backup](https://www.elastic.co/guide/en/elasticsearch/reference/current/snapshots-register-repository.html#snapshots-repository-backup) e.g. on tape?

---

<div class="post-metadata">

**Author:** ![KA3AXCTAH](https://avatars.discourse-cdn.com/v4/letter/k/919ad9/32.png) [@KA3AXCTAH](https://discuss.elastic.co/u/KA3AXCTAH)\
**Post date:** [April 30, 2021, 9:41am UTC](https://discuss.elastic.co/t/unnable-to-list-snapshots-in-elasticsearch-repository/271425/32 "2021-04-30T09:41:33Z")

</div>

yeah, but we do this not every day ;(

---

<div class="post-metadata">

**Author:** ![KA3AXCTAH](https://avatars.discourse-cdn.com/v4/letter/k/919ad9/32.png) [@KA3AXCTAH](https://discuss.elastic.co/u/KA3AXCTAH)\
**Post date:** [April 30, 2021, 9:42am UTC](https://discuss.elastic.co/t/unnable-to-list-snapshots-in-elasticsearch-repository/271425/33 "2021-04-30T09:42:32Z")

</div>

Here's output from the latest version  
looks the same...

```auto
curl -X GET "localhost:9200/_cat/snapshots/temp_elastic_backup?error_trace"

{"error":{"root_cause":[{"type":"parsing_exception","reason":"Failed to parse object: expecting token of type [START_OBJECT] but found [null]","line":1,"col":0,"stack_trace":"ParsingException[Failed to parse object: expecting token of type [START_OBJECT] but found [null]]\n\tat org.elasticsearch.common.xcontent.XContentParserUtils.parsingException(XContentParserUtils.java:71)\n\tat org.elasticsearch.common.xcontent.XContentParserUtils.ensureExpectedToken(XContentParserUtils.java:65)\n\tat org.elasticsearch.repositories.RepositoryData.snapshotsFromXContent(RepositoryData.java:708)\n\tat org.elasticsearch.repositories.blobstore.BlobStoreRepository.getRepositoryData(BlobStoreRepository.java:1706)\n\tat org.elasticsearch.repositories.blobstore.BlobStoreRepository.doGetRepositoryData(BlobStoreRepository.java:1528)\n\tat org.elasticsearch.action.ActionRunnable$2.doRun(ActionRunnable.java:62)\n\tat org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:732)\n\tat org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:26)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630)\n\tat java.base/java.lang.Thread.run(Thread.java:831)\n"}],"type":"repository_exception","reason":"[temp_elastic_backup] Unexpected exception when loading repository data","caused_by":{"type":"parsing_exception","reason":"Failed to parse object: expecting token of type [START_OBJECT] but found [null]","line":1,"col":0,"stack_trace":"ParsingException[Failed to parse object: expecting token of type [START_OBJECT] but found [null]]\n\tat org.elasticsearch.common.xcontent.XContentParserUtils.parsingException(XContentParserUtils.java:71)\n\tat org.elasticsearch.common.xcontent.XContentParserUtils.ensureExpectedToken(XContentParserUtils.java:65)\n\tat org.elasticsearch.repositories.RepositoryData.snapshotsFromXContent(RepositoryData.java:708)\n\tat org.elasticsearch.repositories.blobstore.BlobStoreRepository.getRepositoryData(BlobStoreRepository.java:1706)\n\tat org.elasticsearch.repositories.blobstore.BlobStoreRepository.doGetRepositoryData(BlobStoreRepository.java:1528)\n\tat org.elasticsearch.action.ActionRunnable$2.doRun(ActionRunnable.java:62)\n\tat org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:732)\n\tat org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:26)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630)\n\tat java.base/java.lang.Thread.run(Thread.java:831)\n"},"stack_trace":"RepositoryException[[temp_elastic_backup] Unexpected exception when loading repository data]; nested: ParsingException[Failed to parse object: expecting token of type [START_OBJECT] but found [null]];\n\tat org.elasticsearch.repositories.blobstore.BlobStoreRepository.doGetRepositoryData(BlobStoreRepository.java:1578)\n\tat org.elasticsearch.action.ActionRunnable$2.doRun(ActionRunnable.java:62)\n\tat org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:732)\n\tat org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:26)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630)\n\tat java.base/java.lang.Thread.run(Thread.java:831)\nCaused by: ParsingException[Failed to parse object: expecting token of type [START_OBJECT] but found [null]]\n\tat org.elasticsearch.common.xcontent.XContentParserUtils.parsingException(XContentParserUtils.java:71)\n\tat org.elasticsearch.common.xcontent.XContentParserUtils.ensureExpectedToken(XContentParserUtils.java:65)\n\tat org.elasticsearch.repositories.RepositoryData.snapshotsFromXContent(RepositoryData.java:708)\n\tat org.elasticsearch.repositories.blobstore.BlobStoreRepository.getRepositoryData(BlobStoreRepository.java:1706)\n\tat org.elasticsearch.repositories.blobstore.BlobStoreRepository.doGetRepositoryData(BlobStoreRepository.java:1528)\n\t... 6 more\n"},"status":500}0

```

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [April 30, 2021, 9:54am UTC](https://discuss.elastic.co/t/unnable-to-list-snapshots-in-elasticsearch-repository/271425/34 "2021-04-30T09:54:26Z")

</div>

```auto
RepositoryException[[temp_elastic_backup] Unexpected exception when loading repository data]; nested: ParsingException[Failed to parse object: expecting token of type [START_OBJECT] but found [null]];
        at org.elasticsearch.repositories.blobstore.BlobStoreRepository.doGetRepositoryData(BlobStoreRepository.java:1578)
        at org.elasticsearch.action.ActionRunnable$2.doRun(ActionRunnable.java:62)
        at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:732)
        at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:26)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630)
        at java.base/java.lang.Thread.run(Thread.java:831)
Caused by: ParsingException[Failed to parse object: expecting token of type [START_OBJECT] but found [null]]
        at org.elasticsearch.common.xcontent.XContentParserUtils.parsingException(XContentParserUtils.java:71)
        at org.elasticsearch.common.xcontent.XContentParserUtils.ensureExpectedToken(XContentParserUtils.java:65)
        at org.elasticsearch.repositories.RepositoryData.snapshotsFromXContent(RepositoryData.java:708)
        at org.elasticsearch.repositories.blobstore.BlobStoreRepository.getRepositoryData(BlobStoreRepository.java:1706)
        at org.elasticsearch.repositories.blobstore.BlobStoreRepository.doGetRepositoryData(BlobStoreRepository.java:1528)
        ... 6 more

```

Yes, same problem, just a bit more detail: `expecting token of type [START_OBJECT] but found [null]`.

---

<div class="post-metadata">

**Author:** ![KA3AXCTAH](https://avatars.discourse-cdn.com/v4/letter/k/919ad9/32.png) [@KA3AXCTAH](https://discuss.elastic.co/u/KA3AXCTAH)\
**Post date:** [April 30, 2021, 9:58am UTC](https://discuss.elastic.co/t/unnable-to-list-snapshots-in-elasticsearch-repository/271425/35 "2021-04-30T09:58:21Z")

</div>

so you suggest this is problem on NFS layer (FS, Disk etc)?

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [April 30, 2021, 11:03am UTC](https://discuss.elastic.co/t/unnable-to-list-snapshots-in-elasticsearch-repository/271425/36 "2021-04-30T11:03:55Z")

</div>

I haven't seen the repository contents, but assuming this file is empty I can't see a way for that to have happened without a storage problem (e.g. an `fsync()` was ignored or a rename was not atomic).

---

<div class="post-metadata">

**Author:** ![KA3AXCTAH](https://avatars.discourse-cdn.com/v4/letter/k/919ad9/32.png) [@KA3AXCTAH](https://discuss.elastic.co/u/KA3AXCTAH)\
**Post date:** [April 30, 2021, 11:45am UTC](https://discuss.elastic.co/t/unnable-to-list-snapshots-in-elasticsearch-repository/271425/37 "2021-04-30T11:45:50Z")

</div>

i can send you my repository contents or any specific filesystem info is needed  
thank you so much for you

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [April 30, 2021, 12:52pm UTC](https://discuss.elastic.co/t/unnable-to-list-snapshots-in-elasticsearch-repository/271425/38 "2021-04-30T12:52:37Z")

</div>

I sent you a private message with a link.

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [May 12, 2021, 8:35am UTC](https://discuss.elastic.co/t/unnable-to-list-snapshots-in-elasticsearch-repository/271425/39 "2021-05-12T08:35:15Z")

</div>

Just closing the loop on this one, we investigated further in another channel and determined that there was some bad problem somewhere on the NFS side. The repository listing contained multiple zero-length files:

```nohighlight
-rw-r--r-- 1 elasticsearch elasticsearch 0 Apr 21 07:27 index-66
-rw-r--r-- 1 elasticsearch elasticsearch 0 Apr 21 07:27 index.latest
...
-rw-r--r-- 1 elasticsearch elasticsearch 0 Apr 21 07:27 snap--blahblahblah.dat

```

Elasticsearch writes these files one at a time, and stops on failure, so the only explanation is that the repository is reporting successful writes and then losing the data that was written.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 9, 2021, 8:35am UTC](https://discuss.elastic.co/t/unnable-to-list-snapshots-in-elasticsearch-repository/271425/40 "2021-06-09T08:35:36Z")

</div>

Closed on June 9, 2021, 8:35am UTC

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

[Previous page](https://discuss.elastic.co/t/unnable-to-list-snapshots-in-elasticsearch-repository/271425.md?page=1)
