Click on the ubda disk image in Dashboard and resize it (type in a new size and save changes). If the filesystem is ext2 or ext3, it will be resized to fill the enlarged disk image automatically. For other filesystem types, you have to manually resize to fill the enlarged disk image.

Linode's 'used space' meter shows how much of the space at Linode you're using for your images; it doesn't tell you how much space is free on the images themselves.

Most people will have images that span the amount of space available to them in the account itself, which means that in the LPM it shows as 100% disk usage, with no space free. From Linode's point of view, this is correct; think of it as measuring how much room you have in your account for additional images.

What this means is that of the 8GB of potential space given to you by Linode, you're using 3.88GB for images. The images have to be formatted, which takes away another 100MB or so (for the metadata), leaving you with roughly 3.7GB, which is what shows in your 'df -h' output. Of that 3.7GB, your 'df -h' output shows that you have 288MB free on that image.

You have an additional 4.13GB that you're not using for images, and which won't show up in 'df -h'. You can either do as pclissold suggested and resize your disk image, or you can create a new image to fill the space. You won't be able to share space between the two if you do that though, so be aware of that.

As you can tell, when you migrate machines, the images get copied over exactly, meaning that they're not resized to take advantage of the space, hence why you have space free.

@pclissold:

Click on the ubda disk image in Dashboard and resize it (type in a new size and save changes). If the filesystem is ext2 or ext3, it will be resized to fill the enlarged disk image automatically.

Thanks. That did it.