How do I resize my Linode plan?
We’ll walk you through all the steps necessary for resizing a Linode plan. This involves checking your existing disk space, resizing your existing disk, and resizing your Linode plan. If you are resizing into a larger Linode plan, you can move forward to the third step.
Checking Your Disk Space
When resizing your Linode into a smaller plan the first thing you want to consider is the used disk space on your current plan. We can check how much disk space is being used by running
$ df -h Filesystem Size Used Avail Use% Mounted on udev 488M 0 488M 0% /dev tmpfs 100M 12M 88M 12% /run /dev/sda 25G 1.3G 22G 6% / tmpfs 499M 0 499M 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 499M 0 499M 0% /sys/fs/cgroup tmpfs 100M 0 100M 0% /run/user/1000
You’ll want to ensure your used disk space is smaller than the disk space of the Linode plan you will be resizing into. If you are using more disk space then the new plan allows, you will need to remove any unwanted files. We have a Community post available that may help you in identifying any unwanted files.
Resizing Your Disk
Now that we have confirmed that your disk space will fit with your new plan, we will need to resize the disk of your current plan. Our guide on How to Resize a Linode Disk provides step by step instructions for this. One thing to keep in mind when performing a Disk resize is your Swap disk. When downsizing you want the total of all combined disks to be less than or equal to the new plans disk space.
Resize Your Linode Plan
With the used disk space verified, and the disk resized to fit the new plan, you are now able to resize your Linode Plan. Follow the instructions in our Resizing a Linode guide to complete the process. If you are resizing to a larger Linode plan, Auto-Resize Disk is selected as the default option. You can disable this and resize your disk later if you’d like.
That’s everything you’ll need to do to successfully resize your Linode plan. If you have any questions, please feel free to leave a comment.
Unable to resize it.
- Linode instance is shutdown
- Advanced - Disk - Resize from 360GB to 48896 MB
- Resize operation is queued
- Resize failed
The most likely reason for a failure to resize your disk would be that you have more data on your disk than can be easily rearranged to fit in a smaller space. This happens if the size of the resized disk is the same as or close to the actual amount of data on the disk.
You can get the minimum size your disk can be resized to if you go into the dashboard in the old Linode Manager and look at the error message for the resize operation which reports the smallest number of 4KiB blocks needed to hold the data currently on your disk. Lets say the error reported in the Linode Manager says:
fs_resize: resize failed resize2fs 1.44.0 (7-Mar-2018) /vbin/bin/resize2fs: New size smaller than minimum (1289947)
You will take the number of blocks (1289947) and multiply it by the size of each block (4KiB) and then divide by the number of KiB in a MiB (1024) to get the smallest size your disk can be.
Hint: For this example, I can type in Google's search bar:
1289947 * 4 KiB to MiB or
1289947 * 4 /1024 and get
5 038.85547. I take the answer and round it up to
5039 which is the smallest size I can make my disk in MiB with the amount of data contained on it.
Note: Occasionally the smallest amount may be slightly wrong, so if it still fails to resize, you will want keep to adding a small amount to the answer you get and try again.
My site is too slow.
here is my MTR from your given command from my local IP. (https://pastebin.com/0ZZrvvEx)
then I have run " df -h " this is the output of this command.
[email protected]:~# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/root 96G 94G 1.4G 99% /
devtmpfs 7.9G 0 7.9G 0% /dev
tmpfs 7.9G 0 7.9G 0% /dev/shm
tmpfs 7.9G 753M 7.1G 10% /run
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
cgmfs 100K 0 100K 0% /run/cgmanager/fs
tmpfs 1.6G 0 1.6G 0% /run/user/0
tmpfs 1.6G 0 1.6G 0% /run/user/1002
Help me to increase just SDD if needed,
Before increasing your disc size, why don't you:
- go on "cruft patrol" and delete some stuff you don't need (hint: start with installed packages)…ditto for your database (do you really need all those relation tables?);
- try tuning your web server (both nginix & apache perform pretty badly right out of the box);
- eliminate running services you don't need (do you really need those printer daemons in a virtual environment?);
- look at your site architecture and streamline it (this is going to be especially necessary if you contracted out the development and expected your contractors to do a good job with little/no supervision from you and/or your team);
- etc etc etc
Poor web site performance is rarely the fault of a VPS platform, IMHO…