> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmo/solution/filesystem-doesnt-reflect-instance-resize-ephemeral.md).

# Filesystem Doesn't Reflect Instance Resize (Ephemeral)

## Problem

An OpenStack instance, leveraging an ephemeral, non-boot-from-volume disk for its root partition, has been resized, but, the file system does not reflect the increased size (e.g. according to the\*\*`df`\*\* output).

## Environment

* Platform9 Managed OpenStack - All Versions
* Nova

## Cause

The respective filesystem has yet to be expanded within the guest OS.

## Resolution

### Ext2/3/4

1. Leverage the [resize2fs](https://linux.die.net/man/8/resize2fs) utility to resize the EXT filesystem.

{% tabs %}
{% tab title="None" %}

```none
# resize2fs /dev/sda1
```

{% endtab %}
{% endtabs %}

```
- If the root partition is provisioned using LVM, you may need to expand the associated LV and then specify the path to it on the filesystem, e.g.
```

```
# resize2fs /dev/mapper/vg-root
```

### XFS

1. Leverage the [xfs\_growfs](https://linux.die.net/man/8/xfs_growfs) utility to resize the XFS filesystem.

{% tabs %}
{% tab title="None" %}

```none
# xfs_growfs /dev/sda1
```

{% endtab %}
{% endtabs %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://platform9.com/kb/pmo/solution/filesystem-doesnt-reflect-instance-resize-ephemeral.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.