Resize a Linode

Resize a Linode to a different plan (type). Consider these points before resizing:

  • You can't have an outstanding balance on your account.

  • If any actions are currently running or queued for the Linode, you need to wait for them to complete before you can resize it.

  • The Linode can't be pending migration.

  • The Linode can't have more disk allocation than what the new type supports. If this is the case, you need to delete or resize the disk to be smaller.

  • You can also resize a Linode when using the Rebuild a Linode operation.

  • If you have Block Storage volumes attached to the Linode, you can't resize it to a type that supports fewer volumes. You need to delete volumes from the Linode to meet the limit supported by the smaller type.

Permissions and scopes

To call this operation, you need permissions, based on the model you're using:

  • Identity and access permissions. Your user needs a role with these permissions. Learn more.

    • Permissions: resize_linode
  • OAuth scopes. Your user needs these scopes assigned. Learn more.

    • Scopes: linodes:read_write

CLI

linode-cli linodes resize 123 \
  --type g6-standard-2

Learn more

Path Params
string
enum
required

Enum Call either the v4 URL, or v4beta for operations still in Beta.

Allowed:
integer
required

ID of the Linode to resize.

Body Params
boolean
Defaults to true

Automatically resize disks when resizing a Linode. When resizing down to a smaller plan your Linode's data must fit within the smaller disk size.

string
enum
Defaults to cold

Type of migration used in moving to a new host or Linode type.

warm: the Linode will not power down until the migration is complete.
Warm migrations are not available for DC migrations.

cold: the Linode will be powered down and migrated. When the migration
is complete, the Linode will be powered on.

Allowed:
string
required

The ID representing the Linode Type.

Responses

Language
Credentials
LoadingLoading…
Response
Choose an example:
application/json