# Shard relocation failed due to filesystem read-only

**URL:** <https://discuss.elastic.co/t/shard-relocation-failed-due-to-filesystem-read-only/107709>\
**Category:** Elasticsearch\
**Created:** [November 15, 2017, 9:44am UTC](https://discuss.elastic.co/t/shard-relocation-failed-due-to-filesystem-read-only/107709 "2017-11-15T09:44:56Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![xlc](https://avatars.discourse-cdn.com/v4/letter/x/13edae/32.png) [@xlc](https://discuss.elastic.co/u/xlc)\
**Post date:** [November 15, 2017, 9:44am UTC](https://discuss.elastic.co/t/shard-relocation-failed-due-to-filesystem-read-only/107709/1 "2017-11-15T09:44:56Z")

</div>

Hi,

I'm using elasticsearch2.3.2,many warning log detail appered start from yesterday，like  
[track\_report\_idmonitor\_hour\_17][29] received shard failed for target shard [[track\_report\_idmonitor\_hour\_17][29], node[77MLQROxTgWI-FvwLYEghA], relocating [gnpweLOWTAKcLzKKr8sJJQ], [P], v[42919], s[INITIALIZING], a[id=fYgXh-aHQ6ecl2ctN2nGqA, rId=m0uK\_m-nSiGtarn9udUecg], expected\_shard\_size[20728473815]], indexUUID [nC6QvdOPQkS9oqdmUXrl7Q], message [failed to create shard], failure [ElasticsearchException[failed to create shard]; nested: NotSerializableExceptionWrapper[file\_system\_exception: /ssd1/elasticsearch\_data/track\_report\_production/nodes/0/indices: Read-only file system]; ]

Now，I‘m worried about losing my data,it there some way resolve it safely?By the way, it seems still wirte data successfully.

---

<div class="post-metadata">

**Author:** ![Charles.w](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/charles.w/32/15486_2.png) [@Charles.w](https://discuss.elastic.co/u/Charles.w)\
**Post date:** [November 15, 2017, 10:33am UTC](https://discuss.elastic.co/t/shard-relocation-failed-due-to-filesystem-read-only/107709/2 "2017-11-15T10:33:07Z")

</div>

Hi,

How full your disks are ? Is your filesystem writable by the user running elasticsearch ? Are there any warning in elasticsearch logs indicating a high disk usage ?

On a side note:

- to prevent - or at least be warned - of high disk usage, you can configure the disk allocator : [https://www.elastic.co/guide/en/elasticsearch/reference/2.3/disk-allocator.html](https://www.elastic.co/guide/en/elasticsearch/reference/2.3/disk-allocator.html)
- I do believe than even with full disks this version of elasticsearch can still accept "write" queries as data is being written in the translog prior being written to disk. For more information on the translog : [https://www.elastic.co/guide/en/elasticsearch/reference/2.3/index-modules-translog.html](https://www.elastic.co/guide/en/elasticsearch/reference/2.3/index-modules-translog.html)

Best regards,

Charles Casadei.

---

<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:** [December 13, 2017, 10:33am UTC](https://discuss.elastic.co/t/shard-relocation-failed-due-to-filesystem-read-only/107709/3 "2017-12-13T10:33:16Z")

</div>

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