close

How to safely decrease storage size on CentOS 7 Cloud Servers

  • Author

    Joseph Khaliulin

  • About

    Type
    Tutorial
    Category
    Storage

Posted on 29 April 2024

Decreasing the storage size involves creating a new device with the desired size, transferring all data from the old drive to the new one, and then deleting the old one. This way, all data is kept secure during the operation, and everything gets safely copied as long as it can fit in the target space.

This guide assumes that the root and boot partitions on your Centos 7 storage are not split into separate partitions.

We highly recommend backing up your server before resizing storage!

Create and attach a new storage device

Start creating a new storage device of the preferred size in the UpCloud Control Panel. Note that your server must be shut down before the required options become available.

Go to the Storage section in your server settings and click the Add a new device button underneath the list of your existing storage devices.

jSacLW95 OxS fBZsyTuHmYKIblNkC59oV1cw29joaL ZnpJJCS38Rt1cQOZHjEjOzFc8QZ1vxyoP Bp8WgYBHnHpSPtia4fNyoZjYLsXxrOtvfFvLTLclds - How to safely decrease storage size on CentOS 7 Cloud Servers

In the following dialogue window, select New storage device, give the storage the required size and name, then click the Add a storage device button to confirm.

If you are resizing to a smaller plan, make sure the new storage size matches the storage size offered with the new plan.

B7S6m3qNQZRRY74fYH6ir5qNZRsRkW8Y2yEIxWa1jeAvbDGcCzmxTJTpzg - How to safely decrease storage size on CentOS 7 Cloud Servers

You should now see a second storage device below the original.

U0FFsysQXn7 vfjmcMrkqZ 7IvbChTlSPYH0uzfZmo y8TWsVWaonCv44Zmw89hTz5TjMVixOtgO5 DQb t5TiBfDOzJLT5ngDI23LS07Tz4cKL 7YGcfYCmvKi9 Ejbdp8NQ2kbB0FggzOT5AZHrk - How to safely decrease storage size on CentOS 7 Cloud Servers

After the attaching process is complete, start your server up again.

Once your server is up and running, you can continue resizing at the OS level.

Copying data to the new storage

Check the name of the newly added storage device using the following command.

lsblk

You should see something like this:

NAME   MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 253:0 0 50G 0 disk
└─vda1 253:1 0 50G 0 part /
vdb 253:16 0 25G 0 disk

The device you are looking for is usually the last on the list and will not have partitions on it like vdb in the example above. Create a new partition on the new storage using fdisk. Replace the <disk> in the command below with the new device name.

sudo fdisk /dev/vdb

The utility will open its own command prompt showing Command (m for help): instead of the usual user@host:/$. The following one-letter commands will be entered there.

First, start the new partition wizard with the command n. Use default values by just pressing enter on each of the options, or type in the required parameter if no default value is given.

> n
# Primary p, partition 1, start sector 2048, end sector at disk end.

With the partition created, make it bootable using command a.

> a
# Partition 1 if asked.

Afterwards, you can check that the partition was configured properly and is marked bootable with p. It should show something along the lines of the example underneath.

> p
Device Boot Start End Sectors Size Id Type
/dev/vdb1 * 2048 52428799 52426752 25G 83 Linux

If everything is in order, write partition changes to the storage device using the command w. If there was a mistake in the setup, delete the faulty partition by entering command d and then create a new one with command n.

> w

Once fdisk has finished writing the partition table to the device, it will exit and return you to the usual command prompt. Using the lsblk command, check that the new partition shows up.

lsblk
NAME   MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 253:0 0 50G 0 disk
└─vda1 253:1 0 50G 0 part /
vdb 253:16 0 25G 0 disk
└─vdb1 253:17 0 25G 0 part

You should see both storage devices and their partitions with their correct sizes. The storage will be named similarly to vda or vdb, and their partitions will include the added partition identifier number, e.g. vda1 or vdb1. Notice that some commands below require entering the storage device name while others use the partitions.

Set up the partition using a file system type appropriate for your server. CentOS 7 machines use XFS.

# Creating an XFS file system on CentOS 7.0
sudo mkfs.xfs /dev/vdb1

Afterwards, mount the new storage device on your system so that you can copy the files.

sudo mount /dev/vdb1 /mnt

We recommend using rsync to copy such large amounts of files that your operating system might contain. It provides convenient options for copying all the files from your current storage to the new one while keeping track of the copy process, allowing you to continue from where you left off if you have to cancel the copying.

On the CentOS server, you’ll need to temporarily disable SELinux to allow the copy.

sudo setenforce 0

Install rsync if you do not already have it.

sudo yum install rsync

The rsync command here uses the options for verbose output so that you can easily see what is getting copied. However, having a large amount of output on the display might slow down the process with a larger number of small files.

You can disable the printout by omitting the parameter –v from the command, or having the output redirected to a file by adding ‘> ~/filename.txt‘ to the end of the command.

sudo rsync -avxHAX / /mnt

Once the copy process has finished, check the storage space usage to see everything was copied. The used space will not be exactly the same, but the difference should be minimal.

df

- How to safely decrease storage size on CentOS 7 Cloud Servers

Lastly, install a boot manager on the new storage to boot again with a new main storage device. Depending on your system, you need to install the correct version of GRUB.

Newer CentOS and other Red Hat variants opt for the newer version.

sudo grub2-install /dev/vdb

You should see a confirmation like in the example output below.

Installing for i386-pc platform.
Installation finished. No error reported.

CentOS 7 users should now set the UUID for the new storage device, check it from the /etc/fstab with the following command, and then replace <UUID> in the next command with it while selecting the new partition, vdb1 for example.

sudo umount /mnt
sudo cat /etc/fstab
sudo xfs_admin -U <UUID> /dev/vdb1

After that, shut down your server either with the Shutdown request at your UpCloud Control Panel or by using the following command in your server terminal

sudo shutdown -h now

Swapping storage devices

With your server shut down, go to the Storage tab again and click the eject icon next to the former main storage device, leaving just the new smaller storage device.

GkV7NGqNyLMMEtkTZBO7pePj6UEYa7nbwftTbUc3i KN80l3pjNynb 8mza876T2ENZumzHPsagUs DBvhYAmPWiUx lJ4BuUHzg1XoOWDS6 3aWYJldwp8h1 moRX5phrhh1rw4LMIrNGOoQu cQ - How to safely decrease storage size on CentOS 7 Cloud Servers

If you are resizing to a smaller plan, head to the Plan tab, select the new plan you intend to use and click Save Changes.

iwA09xAZUiiyfKEUJWLX3QRal srcro8g2PjLVjz9olC8QmFJ6kPYMzO8tGcQKcYVRaloglMfv4c501dEpq4ideXRMhdLl N6lmX3oy2skzWyFPN15fbxme5SznSZM3aJx7FNJuTMC4VSViR QHynLs - How to safely decrease storage size on CentOS 7 Cloud Servers

Then, start up your server. Confirm that your data was copied successfully and is available on the new storage device.

If the server cannot find the boot section and fails to start, shut down the server and attach the original storage again to boot from. Then, reinstall the GRUB and try booting from the new device again by detaching the old one.

Afterwards, you can delete the old storage from your UpCloud Control Panel in the Storage device section. If you no longer need it, be sure also to delete the backup you took.

Discussion

Leave a Reply

Your email address will not be published. Required fields are marked *

Try out today!

Start your free 14-day trial today and discover why thousands of businesses trust UpCloud

  • Risk-free trial
  • Optimized performance
  • Scalable infrastructure
  • Top-tier security
  • Global availability

Sign up

Back to top