** Changed in: cloud-initramfs-tools (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: cloud-utils (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-initramfs-tools in
Hi Ben,
Thanks very much for testing this out.
I've run that image on Brightbox Cloud and it takes 5 mins 25 seconds from
issuing the 'create' command to the ssh being available with a 2TB disk. So
that's including all the server provisioning, cloud-init key metadata stuff
and the initial login
** Changed in: cloud-initramfs-tools (Ubuntu)
Importance: Undecided = Low
** Changed in: cloud-utils (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/955272
In testing mkfs.ext4 -E resize=536870912, it results in no additional
space utilization, while allowing a full resize to 2TB. My test case was
to create a two new 2G filesystems, copy over a cloud image root.tar.gz
to both, then resize one to 2TB.
/dev/loop1 2.0G 803M 1.1G 42%
I might add that my test was for an offline resize, not an online
resize. In testing, an 2GB ext4 filesystem can be resized to 2TB with
out the -E resize... option.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In attempting to repo this using real disks on EC2 (4x 450GB ephemeral
storage devices in LVM configuration), the resize times are truly
dreadful. I have to question the utility in resizing a small cloud image
to a massive image as it took nearly 45 minutes to do an online resize.
But I have been
The workaround is to create a 128M journal via
mkfs.ext4 -J size=128
which is the size of journal generally created on a 20G disk anyway.
This costs 24k blocks (96M) on a 1G partition - which is about 10% of
the free blocks available.
When you do this Oneiric's resize2fs now appears to
Same problem on precise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/955272
Title:
resize2fs fail with very large disks from small source image
To manage notifications about this bug go to:
Online resize still fails:
ubuntu@srv-eej0z:~$ sudo resize2fs /dev/loop0
resize2fs 1.42 (29-Nov-2011)
Filesystem at /dev/loop0 is mounted on /mnt; on-line resizing required
old_desc_blocks = 1, new_desc_blocks = 80
Performing an on-line resize of /dev/loop0 to 335544320 (4k) blocks.
resize2fs:
I've logged bug #956038 for the failure of resize2fs to check the
maximum size of the filesystem.
The workaround is to allocate the maximum number of resize blocks with:
mkfs.ext4 -J size=128 -E resize=4294967295 -F tiny
The '2^32-1' number is to workaround faults in older versions of
'mke2fs'.
10 matches
Mail list logo
