# Failed shard error on elasticsearch snapshot (No space left)

**URL:** https://discuss.elastic.co/t/failed-shard-error-on-elasticsearch-snapshot-no-space-left/284035
**Category:** Kibana
**Tags:** snapshot-and-restore
**Created:** [September 13, 2021, 9:16am UTC](https://discuss.elastic.co/t/failed-shard-error-on-elasticsearch-snapshot-no-space-left/284035 "2021-09-13T09:16:45Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Prasad\_94](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/prasad_94/32/94465_2.png) [@Prasad\_94](https://discuss.elastic.co/u/Prasad_94)
#### Post date: [September 13, 2021, 9:16am UTC](https://discuss.elastic.co/t/failed-shard-error-on-elasticsearch-snapshot-no-space-left/284035/1 "2021-09-13T09:16:45Z")

</div>

Hi all,

When I navigate to stack management --\> snapshots and repositories I can see the snapshots list.

On that list, there is a one-column that said Failed shards.

Right now most of the snapshots show 1 failed shard in there. And when I check the summary (Kibana GUI) of that snapshot it shows the below error.

INTERNAL\_SERVER\_ERROR: ElasticsearchException[failed to create blob container]; nested: FileSystemException[: No space left on device]

We have separate storage to store these archived indexes and it has more than 150 + GB of available space right now.

Does anyone have an idea about why are we getting this error?

Regards.

---

<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: [October 11, 2021, 9:17am UTC](https://discuss.elastic.co/t/failed-shard-error-on-elasticsearch-snapshot-no-space-left/284035/2 "2021-10-11T09:17:05Z")

</div>

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