> For the complete documentation index, see [llms.txt](https://docs.platform9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform9.com/managed-openstack/5.8/troubleshooting/linux-kvm/troubleshooting-fs-resize-selinux.md).

# File System Resize Issues With Scientific Linux 6.x

This article describes the process to prepare your Scientific Linux virtual machine image, for file system resize to work.

{% hint style="info" %}
**Note**

This process has been testing with Scientific Linux version 6.6. If you are experiencing issues with file system resize for a different version of Scientific Linux, please contact <support@platform9.com>.
{% endhint %}

In order for file system resize to work with OpenStack, you need single partition setup. **No LVM**

To prepare the image follow these steps:

### Step 1 - (If not configured already) Add EPEL repository to the set of configured repositories.

### Step 2 - Install cloud-utils, cloud-init and dracut-modules-growroot packages

{% tabs %}
{% tab title="Scientific Linux" %}

```none
yum install -y cloud-utils cloud-init dracut-modules-growroot
```

{% endtab %}
{% endtabs %}

### Step 3 - Rebuild the Operating System Kernel Image

First backup the kernel image

{% tabs %}
{% tab title="Scientific Linux" %}

```none
cp /boot/initramfs-`uname -r`.img /boot/initramfs-`uname -r`.img.bak
```

{% endtab %}
{% endtabs %}

Then rebuild the image

{% tabs %}
{% tab title="Scientific Linux" %}

```none
dracut -f
```

{% endtab %}
{% endtabs %}

### Step 4 - Copy VM Image to Platform9 Image Catalog

At this point, the VM Image is ready. Power off the VM. Copy the VM Image to imagelibrary data directory on the host that's assigned Image Library role.

Upon creating an instance with this image, the growroot function kicks in during startup and grows to root volume to size of disk allocated.


---

# 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 by asking a question.

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

```
GET https://docs.platform9.com/managed-openstack/5.8/troubleshooting/linux-kvm/troubleshooting-fs-resize-selinux.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 `automate deployments from our CI pipeline` 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.