# Indices Created in New Node after Disk Extend **URL:** \ **Category:** Elasticsearch\ **Created:** [March 8, 2016, 3:22pm UTC](https://discuss.elastic.co/t/indices-created-in-new-node-after-disk-extend/43794 "2016-03-08T15:22:18Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Ben19](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ben19/32/3745_2.png) [@Ben19](https://discuss.elastic.co/u/Ben19)\ **Post date:** [March 8, 2016, 3:22pm UTC](https://discuss.elastic.co/t/indices-created-in-new-node-after-disk-extend/43794/1 "2016-03-08T15:22:18Z")
Hi, we recently ran out of volume space on one of our cluster servers, we extended the diLVM volume as normal but now we notice that after the extend (plus a reboot) that any new indices are now created under /nodes/1/indices and not /nodes/0/indices and such are not loaded into ES. Is there a way to change back to the previous node or migrate the data across to the new one so it’s searchable via KB? Thanks ---
**Author:** ![Ben19](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ben19/32/3745_2.png) [@Ben19](https://discuss.elastic.co/u/Ben19)\ **Post date:** [March 23, 2016, 11:19am UTC](https://discuss.elastic.co/t/indices-created-in-new-node-after-disk-extend/43794/2 "2016-03-23T11:19:59Z")
Anyone believe they may be able to help with this? Since then our cluster has been unstable and noted a number of issues like below: Caused by: java.nio.file.FileSystemException: /var/lib/elasticsearch/elasticsearch/nodes/0/indices/devicename-2016.02.21/4/index: Too many open files TranslogException[failed to create new translog file]; nested: FileAlreadyExistsException[/var/lib/elasticsearch/elasticsearch/nodes/0/indices/devicename-2016.03.21/1/translog/translog-17.tlog] ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 11:05pm UTC](https://discuss.elastic.co/t/indices-created-in-new-node-after-disk-extend/43794/3 "2017-07-05T23:05:54Z")