{"id":1957,"date":"2024-04-29T12:53:44","date_gmt":"2024-04-29T09:53:44","guid":{"rendered":"https:\/\/upcloud.com\/global\/us\/resources\/tutorials\/decrease-storage-size-centos-7\/"},"modified":"2024-04-29T12:53:44","modified_gmt":"2024-04-29T09:53:44","slug":"decrease-storage-size-centos-7","status":"publish","type":"tutorial","link":"https:\/\/upcloud.com\/global\/resources\/tutorials\/decrease-storage-size-centos-7\/","title":{"rendered":"How to safely decrease storage size on CentOS 7 Cloud Servers"},"content":{"rendered":"\n

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.<\/p>\n\n\n\n

This guide assumes that the root and boot partitions on your Centos 7 storage are not split into separate partitions.<\/p>\n\n\n\n

We highly recommend backing up<\/b> your server before resizing storage!<\/p>\n\n\n\n

Create and attach a new storage device<\/h2>\n\n\n\n

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.<\/p>\n\n\n\n

Go to the Storage<\/em> section in your server settings and click the Add a new device<\/em> button underneath the list of your existing storage devices.<\/p>\n\n\n\n

\"-\"<\/p>\n\n\n\n

In the following dialogue window, select New storage device<\/em>, give the storage the required size and name, then click the Add a storage device<\/em> button to confirm.<\/p>\n\n\n\n

If you are resizing to a smaller plan, make sure the new storage size matches the storage size offered with the new plan.<\/p>\n\n\n\n

\"-\"<\/figure>\n\n\n\n

You should now see a second storage device below the original.<\/p>\n\n\n\n

\"-\"<\/figure>\n\n\n\n

After the attaching process is complete, start your server up again.<\/p>\n\n\n\n

Once your server is up and running, you can continue resizing at the OS level.<\/p>\n\n\n\n

Copying data to the new storage<\/h2>\n\n\n\n

Check the name of the newly added storage device using the following command.<\/p>\n\n\n\n

lsblk<\/code><\/pre>\n\n\n\n
You should see something like this:<\/p>\n\n\n\n
NAME   MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda    253:0   0  50G  0  disk
\u2514\u2500vda1 253:1   0  50G  0  part \/
vdb    253:16  0  25G  0  disk<\/code><\/pre>\n\n\n\n
The device you are looking for is usually the last on the list and will not have partitions on it like vdb<\/em> in the example above. Create a new partition on the new storage using fdisk. Replace the <disk><\/em> in the command below with the new device name.<\/p>\n\n\n\n
sudo fdisk \/dev\/vdb<\/code><\/pre>\n\n\n\n
The utility will open its own command prompt showing Command (m for help):<\/em> instead of the usual user@host:\/$.<\/em> The following one-letter commands will be entered there.<\/p>\n\n\n\n
First, start the new partition wizard with the command n<\/em><\/strong>. Use default values by just pressing enter on each of the options, or type in the required parameter if no default value is given.<\/p>\n\n\n\n
> n
# Primary p, partition 1, start sector 2048, end sector at disk end.<\/code><\/pre>\n\n\n\n
With the partition created, make it bootable using command a<\/em><\/strong>.<\/p>\n\n\n\n
> a
# Partition 1 if asked.<\/code><\/pre>\n\n\n\n
Afterwards, you can check that the partition was configured properly and is marked bootable with p<\/em><\/strong>. It should show something along the lines of the example underneath.<\/p>\n\n\n\n
> p
Device     Boot Start      End  Sectors  Size Id Type
\/dev\/vdb1  *     2048 52428799 52426752   25G 83 Linux<\/code><\/pre>\n\n\n\n
If everything is in order, write partition changes to the storage device using the command w<\/em><\/strong>. If there was a mistake in the setup, delete the faulty partition by entering command d<\/strong> and then create a new one with command n<\/strong><\/em>.<\/p>\n\n\n\n
> w<\/code><\/pre>\n\n\n\n
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<\/em> command, check that the new partition shows up.<\/p>\n\n\n\n
lsblk<\/code><\/pre>\n\n\n\n
NAME   MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda    253:0   0  50G  0  disk
\u2514\u2500vda1 253:1   0  50G  0  part \/
vdb    253:16  0  25G  0  disk
\u2514\u2500vdb1 253:17  0  25G  0  part<\/code><\/pre>\n\n\n\n
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.<\/b> Notice that some commands below require entering the storage device name while others use the partitions.<\/p>\n\n\n\n
Set up the partition using a file system type appropriate for your server. CentOS 7 machines use XFS.<\/p>\n\n\n\n
# Creating an XFS file system on CentOS 7.0
sudo mkfs.xfs \/dev\/vdb1<\/code><\/pre>\n\n\n\n
Afterwards, mount the new storage device on your system so that you can copy the files.<\/p>\n\n\n\n
sudo mount \/dev\/vdb1 \/mnt<\/code><\/pre>\n\n\n\n
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.<\/p>\n\n\n\n
On the CentOS server, you\u2019ll need to temporarily disable SELinux to allow the copy.<\/p>\n\n\n\n
sudo setenforce 0<\/code><\/pre>\n\n\n\n
Install rsync if you do not already have it.<\/p>\n\n\n\n
sudo yum install rsync<\/code><\/pre>\n\n\n\n
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.<\/p>\n\n\n\n
You can disable the printout by omitting the parameter \u2013v<\/em> from the command, or having the output redirected to a file by adding \u2018> ~\/filename.txt<\/em>\u2018 to the end of the command.<\/p>\n\n\n\n
sudo rsync -avxHAX \/ \/mnt<\/code><\/pre>\n\n\n\n
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.<\/p>\n\n\n\n
df<\/code><\/pre>\n\n\n\n
\"-\"<\/p>\n\n\n\n
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.<\/p>\n\n\n\n
Newer CentOS and other Red Hat variants opt for the newer version.<\/p>\n\n\n\n
sudo grub2-install \/dev\/vdb<\/code><\/pre>\n\n\n\n
You should see a confirmation like in the example output below.<\/p>\n\n\n\n
Installing for i386-pc platform.
Installation finished. No error reported.<\/code><\/pre>\n\n\n\n
CentOS 7 users should now set the UUID for the new storage device, check it from the \/etc\/fstab<\/em> with the following command, and then replace <UUID><\/em> in the next command with it while selecting the new partition, vdb1<\/em> for example.<\/p>\n\n\n\n
sudo umount \/mnt
sudo cat \/etc\/fstab
sudo xfs_admin -U <UUID> \/dev\/vdb1<\/code><\/pre>\n\n\n\n
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<\/p>\n\n\n\n
sudo shutdown -h now<\/code><\/pre>\n\n\n\n
Swapping storage devices<\/h2>\n\n\n\n
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.<\/p>\n\n\n\n
\"-\"<\/figure>\n\n\n\n
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.<\/p>\n\n\n\n
\"-\"<\/figure>\n\n\n\n
Then, start up your server. Confirm that your data was copied successfully and is available on the new storage device.<\/p>\n\n\n\n
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.<\/p>\n\n\n\n
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.<\/p>\n","protected":false},"author":65,"featured_media":39576,"comment_status":"open","ping_status":"closed","template":"","community-category":[265],"class_list":["post-1957","tutorial","type-tutorial","status-publish","has-post-thumbnail","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/upcloud.com\/global\/wp-json\/wp\/v2\/tutorial\/1957","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/upcloud.com\/global\/wp-json\/wp\/v2\/tutorial"}],"about":[{"href":"https:\/\/upcloud.com\/global\/wp-json\/wp\/v2\/types\/tutorial"}],"author":[{"embeddable":true,"href":"https:\/\/upcloud.com\/global\/wp-json\/wp\/v2\/users\/65"}],"replies":[{"embeddable":true,"href":"https:\/\/upcloud.com\/global\/wp-json\/wp\/v2\/comments?post=1957"}],"version-history":[{"count":0,"href":"https:\/\/upcloud.com\/global\/wp-json\/wp\/v2\/tutorial\/1957\/revisions"}],"wp:attachment":[{"href":"https:\/\/upcloud.com\/global\/wp-json\/wp\/v2\/media?parent=1957"}],"wp:term":[{"taxonomy":"community-category","embeddable":true,"href":"https:\/\/upcloud.com\/global\/wp-json\/wp\/v2\/community-category?post=1957"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}