# Elasticsearch Datase

**URL:** https://discuss.elastic.co/t/elasticsearch-datase/382609
**Category:** Elastic Labs
**Created:** [October 12, 2025, 4:13pm UTC](https://discuss.elastic.co/t/elasticsearch-datase/382609 "2025-10-12T16:13:08Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![galuh\_tirta](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/galuh_tirta/32/126713_2.png) [@galuh\_tirta](https://discuss.elastic.co/u/galuh_tirta)
#### Post date: [October 12, 2025, 4:13pm UTC](https://discuss.elastic.co/t/elasticsearch-datase/382609/1 "2025-10-12T16:13:08Z")

</div>

Hello everyone,

I need some help for a discussion:

I have an Elasticsearch cluster running with three nodes: node 1, node 2, and node 3.

- Node 1 is the master node

- Node 2 is the hot node

- Node 3 is the warm node

Currently, node 2's storage is almost full at 97%.

I decided to add more storage from ESXi because I still have 1TB of free storage there.

After mounting the new storage to node 2, I accidentally ran `fdisk /dev/sdb` and wrote to it.

Without realizing, `/dev/sdb` was already part of an LVM, which caused the LVM to go missing.

However, Elasticsearch is still running normally at this moment.

My question is: what is the impact if I run

```auto
sudo vgreduce --removemissing --force ubuntu-vg

```

considering that `/var/lib/elasticsearch` is also on the same volume group?

If I run that command, will Elasticsearch crash?

 ![Screenshot_2025-10-12-20-51-44-227_com.microsoft.rdc.androidx](https://us1.discourse-cdn.com/elastic/original/3X/d/2/d2ff2ad975e573c61527d5c334b406811b54368f.jpeg)