Increase root partition to prevent alert in array

[mprinvale]

We have an alert "rs low space in root partition" and it keeps getting triggered during load tests.

# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda1             9.9G  9.4G     0 100% /
/dev/sdb              414G  199M  393G   1% /mnt
none                  3.8G     0  3.8G   0% /dev/shm

We have plenty of space but I'm not sure how to allocate more space to the sda1 during boot up. Any help would be great.

Thanks

[Ryan - RightScale]

/dev/sda is the root volume of the instance and it is limited to 10GB only for S3 backed instances. The only way to expand the volume would be to create a new base image with a root volume that is EBS backed.

[Chris Fordham - RightScale]

Originally Posted by mprinvale

We have an alert "rs low space in root partition" and it keeps getting triggered during load tests.

# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda1             9.9G  9.4G     0 100% /
/dev/sdb              414G  199M  393G   1% /mnt
none                  3.8G     0  3.8G   0% /dev/shm

We have plenty of space but I'm not sure how to allocate more space to the sda1 during boot up. Any help would be great.

Thanks

When issuing he df -m or just df commands, you will see the ~500GB available in the root filesystem as the -h will round the value down to 0GB.
A number of ServerTemplates are published with an alert for low disk space to be 1GB or less - this is fine for some servers but may indicate a gradual fill for others.
The simple solution if 500GB is nothing to worry about, is to modify the alert on your template and server to be less sensitive, e.g. 100MB.

Generally, it is not recommended using a larger image/root filesystem unless the extra data is not media i.e. non-ephemeral data should be stored and backed up on EBS volumes/snapshots or a remote file store such as S3.
It is rare that system files e.g. extra software installed will fill a 10GB image.

[mprinvale]

Thanks for the replies and help!