huh,
root@undercloud-notcompute-jws3awlsb2kh:/home/heat-admin# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 1.8T 0 disk
��sda1 8:1 0 20G 0 part /
��sda2 8:2 0 7.9M 0 part
root@undercloud-notcompute-jws3awlsb2kh:/home/heat-admin# fdisk /dev/sda
Command (m for help): p
Disk /dev/sda: 2000.4 GB, 2000365379584 bytes
255 heads, 63 sectors/track, 243197 cylinders, total 3906963632 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000233a6
Device Boot Start End Blocks Id System
/dev/sda1 1 41945714 20972857 83 Linux
/dev/sda2 41945715 41961779 8032+ 82 Linux swap / Solaris
This would have been the same for the raring image, so a mere 20G
partition size was enough to trigger the failure. That should be
reproducable in virt.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1233075
Title:
resizefs failure with raring
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1233075/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
