Written by Landis Arnold on . Turnkey Linux

Turnkeylinux Hosting - volume size changes

I have hosted Turnkeylinux images in the following ways

At present I am hosting nearly everything on Linode, though for the sake of speed and the ability to "turnoff" (and not be charged when not running) I am running a few servers also on the AWS based TKL Hub.

A few caveats.  Linode, if using their Kernel, will resize Drive Image sizes along with FileSystem Sizes very well.

It takes some work to do this on the TKL Hub - this is the current HOW To:

https://www.turnkeylinux.org/docs/expand-existing-root-volume-size

though I would skip the AWS section and just clone bigger, but then still do all of the following in SSH.

To be most specific:  

gdisk /dev/xvda
parted
print
fix
resizepart
resize2fs /dev/xvda2

Instructions in the link above have "

"gdisk -1 /dev/xvda " and I had just now to skip the -1 to get it to work.
It would be better if everything just "resized" and it might be easiest to use TKLBAM for that just installing a bigger instance.

All things considered, Linode Feels "more like mine". but it is still important to learn different systems from time to time.

Bear Metal is somewhat going away.  So much work and energy to maintain a server these days.

Print

Joomla3 Appliance - Powered by TurnKey Linux