disk resize terribly slow on azure

[Scott Moser]

I just launched a 12.04 instance with azure cmdline tools:

azure vm create --vm-size=extrasmall --vm-name=smoser0912pr-hack2 "--location=East US" --<email address hidden> --no-ssh-password --ssh=22 --custom-data=/tmp/my-userdata.txt smoser0912pr-hack2 b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-12_04_3-LTS-amd64-server-20130909-en-us-30GB smoser

/var/log/cloud-init.log shows:

2013-09-12 20:35:40,568 - __init__.py[DEBUG]: handling resizefs with freq=None and args=[]
2013-09-12 20:37:31,234 - cc_resizefs.py[DEBUG]: resize took 110.654913902 seconds
2013-09-12 20:37:31,234 - cc_resizefs.py[DEBUG]: resizing root filesystem (type=ext4, maj=8, min=1, val=True)

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: cloud-init 0.6.3-0ubuntu1.6
ProcVersionSignature: Ubuntu 3.2.0-53.81-virtual 3.2.50
Uname: Linux 3.2.0-53-virtual x86_64
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
Date: Thu Sep 12 20:37:45 2013
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install)

[Ben Howard (darkmuggle-deactivatedaccount)]

Assinging this to me.

[Scott Moser (smoser)]

just for info, i launched images of
 Ubuntu-12_04_2-LTS-amd64-server-20130624-en-us-30GB
 Ubuntu-12_04_3-LTS-amd64-server-20130827-en-us-30GB

They had resize root times of 95.1887409687 and 94.2440910339 respectfully.

so at least this isn't a regression.
Its possible, then that it is really just bug 1179610.

However in all other cases I'd seen that was only a 10x performance increase, where on 12.04 versus 13.10, we're seeing more like a 100x difference.

One thing that ew can do to fix this anyway is just resize the disk before registering it.
since 30G is minimum size, it does'nt make much sense to put a filesystem on the disk with 2G and resize on every instance launch.

[Ben Howard (darkmuggle-deactivatedaccount)]

Scheduling work for this cycle. For Precise, we'll just do a full disk population instead of cheating.

[Ben Howard (darkmuggle-deactivatedaccount)]

This was fixed a long time ago....