# Can't start node (out of space) and can't move shards because I can't start the node **URL:** \ **Category:** Elasticsearch\ **Created:** [July 19, 2020, 8:41pm UTC](https://discuss.elastic.co/t/cant-start-node-out-of-space-and-cant-move-shards-because-i-cant-start-the-node/241813 "2020-07-19T20:41:32Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![pushshift](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pushshift/32/50408_2.png) [@pushshift](https://discuss.elastic.co/u/pushshift)\ **Post date:** [July 19, 2020, 8:41pm UTC](https://discuss.elastic.co/t/cant-start-node-out-of-space-and-cant-move-shards-because-i-cant-start-the-node/241813/1 "2020-07-19T20:41:33Z")
I am in a bit of a bind. One of the nodes on my cluster ran out of space. I can't start elasticsearch because there is no space left. I'm unable to move or delete shards / indices from that node because I can't start Elasticsearch. What are my options? Can I symlink some folders under the data directory to a larger drive? I'm not sure how to proceed. ---
**Author:** ![Steve\_Mushero](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steve_mushero/32/22441_2.png) [@Steve\_Mushero](https://discuss.elastic.co/u/Steve_Mushero)\ **Post date:** [July 20, 2020, 7:51am UTC](https://discuss.elastic.co/t/cant-start-node-out-of-space-and-cant-move-shards-because-i-cant-start-the-node/241813/2 "2020-07-20T07:51:18Z")
You can't find any space, by deleting logs or unused yum caches or anything to free up a bit of space, or is this no space on the file system hosting ES? Yes, one thing is just get bigger drive and copy over all the data (we did that) but can take a long time. I'd think you could symlink a few big files, but would have to test - others probably have more insights; regardless, snapshot first if you can (in cloud, etc.). Also make sure no root space allocated, which varies by your linux, file system type, etc.: > **[How To Free Reserved Space On EXT4 Partitions](https://odzangba.wordpress.com/2010/02/20/how-to-free-reserved-space-on-ext4-partitions/)** > > This one came in handy when I bought a 1TB hard drive last week. Most linux distributions reserve 5% of new partitions for the root user and system services. The idea here is even when you run out … ---
**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:** [July 20, 2020, 11:10am UTC](https://discuss.elastic.co/t/cant-start-node-out-of-space-and-cant-move-shards-because-i-cant-start-the-node/241813/3 "2020-07-20T11:10:43Z")
Elasticsearch has a bunch of protection in place to prevent a node from consuming every bit of available disk space, so my guess is that something else filled the disk up. If so, as Steve says, clear out that other stuff. I don't think symlinks will work, no, the security manager shouldn't allow that. There's no user-serviceable parts inside the data directory so we very much recommend against moving anything around as you suggest. Is your cluster health `yellow`? If so, perhaps the simplest path forward is to wipe the node and start again. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 17, 2020, 11:10am UTC](https://discuss.elastic.co/t/cant-start-node-out-of-space-and-cant-move-shards-because-i-cant-start-the-node/241813/4 "2020-08-17T11:10:44Z")
Closed on August 17, 2020, 11:10am UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.