** Changed in: cloud-init
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/961226
Title:
cloud-init should run resize2fs in the
This bug was fixed in the package cloud-init - 0.6.3~bzr551-0ubuntu1
---
cloud-init (0.6.3~bzr551-0ubuntu1) precise; urgency=low
* New upstream snapshot.
* support running resize2fs in the background (default=off) (LP: #961226)
-- Scott Moser smo...@ubuntu.com Thu, 22 Mar
** Branch linked: lp:cloud-init
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/961226
Title:
cloud-init should run resize2fs in the background
To manage notifications about
** Also affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/961226
Title:
cloud-init should run resize2fs in the
The particular development platform I was trying this has an I/O speed
about the same as a floppy disk drive, so this is perhaps not as
important as one might think. However, it might still be useful as a
feature to speed up boot time.
--
You received this bug notification because you are a
I've decided to turn this into a config option and leave it off by
default (block on resize2fs).
this is pretty much worst possible scenario for io
* on disk file was stored as 1.4G ish (possibly larger, but sparse)
* hypervisor grows it to some larger size (10 or 20G or something) but
