You are here:

Hi,
I'd simply like to launch a turnkey instance that has more than 10 gigs from start, I don't want to mess around afterwards. I have a joomla site that is over 20 gigs and want to migrate it,
Cheers,
Dom

Right, so you want the root filesystem to be larger than 10GBs.
Unfortunately, the way Amazon EC2 works that is easier said than done.
You'd have to create an entirely new image. We could program the Hub
to do that but then you'd have to wait much longer for your machine to
come up. Much longer.

Instead I propose you create an EBS volume and mount --bind it to
wherever you want on your system. See this tutorial on how to move data
to instance storage. Moving
parts of your filesystem off to an EBS volume is similar in principle.

And AFAIK (for the purposes of this) it is irrelevant whether you have an S3 or EBS backed instance.

Basically you should be able to use almost exactly the same commands as are used in the example Liraz linked to, but substitute /path/to/big/Joomla/folder (where ever that is) for /home in the example.

Well I tried using the webmin method first and it cam up with this when I replace /home with /var/www

Failed to save mount : Missing or non-existant original directory

I then used the shell methid by using these commands:

mv /var/www /mnt

mkdir -p /var/www

echo /mnt/var/www /var/www bind bind 0 0 >> /etc/fstab

mount /var/www

It moved the var/www and subdirectories to /mnt successfully, but doesn't seem to recognise them. In the disk and netword file system webmin module it describes them as not in use, when I click to try to activate it comes up with:

Failed to mount /var/www :

mount: special device /mnt/var/www does not exist

So although the folder seems to be in the right place it's not being recognised!