2012-02-21 01:28:37 |
Scott Moser |
bug |
|
|
added bug |
2012-02-21 01:31:13 |
Scott Moser |
attachment added |
|
failed console log (some user-data output clipped) https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/937352/+attachment/2764046/+files/console-i-0000148c.log |
|
2012-02-21 01:31:40 |
Scott Moser |
attachment added |
|
successful console log https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/937352/+attachment/2764047/+files/console-i-0000148d.log |
|
2012-02-21 01:43:27 |
Scott Moser |
description |
Not a dupe of bug 906722, but it seems very similar.
Occasionally on openstack clouds, we're seeing the root partition not being/grown on first-boot as it should be.
This was reported, and I have observed it on precise alpha-2 and will attach console logs. It happens sporadically.
The output of the relevant section of initramfs in the failed case looks like this:
| Begin: Running /scripts/init-premount ... done.
| Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
| Begin: Running /scripts/local-premount ... done.
| [ 0.940836] EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null)
| Begin: Running /scripts/local-bottom ... [ 0.955771] FDC 0 is a S82078B
| [ 1.012874] vda: vda1
| GROWROOT: WARNING: resize failed: FAILED: failed to resize
| ***** WARNING: Resize failed, attempting to revert ******
| Re-reading the partition table ...
| BLKRRPART: Device or resource busy
| The command to re-read the partition table failed.
| Run partprobe(8), kpartx(8) or reboot your system now,
| before using mkfs
| ***** Appears to have gone OK ****
| [ 1.114017] EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null)
| done.
| done.
| Begin: Running /scripts/init-bottom ... done.
In the successful case, it looks like this:
| Begin: Running /scripts/init-premount ... done.
| Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
| Begin: Running /scripts/local-premount ... done.
| [ 1.035664] EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null)
| Begin: Running /scripts/local-bottom ... [ 1.052365] FDC 0 is a S82078B
| [ 1.094201] vda: vda1
| [ 1.135831] vda: vda1
| GROWROOT: CHANGED: partition=1 start=16065 old: size=4176900 end=4192965 new: size=20948760,end=20964825
| [ 1.164067] Refined TSC clocksource calibration: 2532.595 MHz.
| [ 1.202383] EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null)
| done.
| done.
| Begin: Running /scripts/init-bottom ... done.
The code that is running here is growroot/scripts/local-bottom/growroot [1]
--
[1] http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/cloud-initramfs-tools/precise/view/head:/growroot/scripts/local-bottom/growroot |
Not a dupe of bug 906722, but it seems very similar.
Occasionally on openstack clouds, we're seeing the root partition not being/grown on first-boot as it should be.
This was reported, and I have observed it on precise alpha-2 and will attach console logs. It happens sporadically.
The output of the relevant section of initramfs in the failed case looks like this:
| Begin: Running /scripts/init-premount ... done.
| Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
| Begin: Running /scripts/local-premount ... done.
| [ 0.940836] EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null)
| Begin: Running /scripts/local-bottom ... [ 0.955771] FDC 0 is a S82078B
| [ 1.012874] vda: vda1
| GROWROOT: WARNING: resize failed: FAILED: failed to resize
| ***** WARNING: Resize failed, attempting to revert ******
| Re-reading the partition table ...
| BLKRRPART: Device or resource busy
| The command to re-read the partition table failed.
| Run partprobe(8), kpartx(8) or reboot your system now,
| before using mkfs
| ***** Appears to have gone OK ****
| [ 1.114017] EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null)
| done.
| done.
| Begin: Running /scripts/init-bottom ... done.
In the successful case, it looks like this:
| Begin: Running /scripts/init-premount ... done.
| Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
| Begin: Running /scripts/local-premount ... done.
| [ 1.035664] EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null)
| Begin: Running /scripts/local-bottom ... [ 1.052365] FDC 0 is a S82078B
| [ 1.094201] vda: vda1
| [ 1.135831] vda: vda1
| GROWROOT: CHANGED: partition=1 start=16065 old: size=4176900 end=4192965 new: size=20948760,end=20964825
| [ 1.164067] Refined TSC clocksource calibration: 2532.595 MHz.
| [ 1.202383] EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null)
| done.
| done.
| Begin: Running /scripts/init-bottom ... done.
The code that is running here is growroot/scripts/local-bottom/growroot [1], growpart is part of cloud-utils [2].
Other relevant info, in at least one case, a reboot got the partition resized.
--
[1] http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/cloud-initramfs-tools/precise/view/head:/growroot/scripts/local-bottom/growroot
[2] http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/cloud-utils/precise/view/head:/bin/growpart |
|
2012-02-21 03:49:55 |
Scott Moser |
attachment added |
|
script mimicking initramfs behavior https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/937352/+attachment/2764316/+files/go-sfdisk-crazy |
|
2012-02-21 10:20:05 |
Andrew Glen-Young |
bug |
|
|
added subscriber The Canonical Sysadmins |
2012-02-21 15:48:55 |
Launchpad Janitor |
cloud-initramfs-tools (Ubuntu): status |
New |
Confirmed |
|
2012-02-24 07:30:02 |
Launchpad Janitor |
cloud-initramfs-tools (Ubuntu): status |
Confirmed |
Fix Released |
|
2012-02-24 08:12:17 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/cloud-initramfs-tools |
|
2012-02-28 15:03:13 |
Scott Moser |
summary |
root partition in may not be grown |
root partition may not be grown |
|
2012-02-28 15:03:32 |
Scott Moser |
cloud-initramfs-tools (Ubuntu): status |
Fix Released |
In Progress |
|
2012-02-28 18:30:50 |
Scott Moser |
bug task added |
|
cloud-utils |
|
2012-02-28 18:31:04 |
Scott Moser |
bug task added |
|
cloud-utils (Ubuntu) |
|
2012-02-28 19:04:57 |
Launchpad Janitor |
branch linked |
|
lp:cloud-utils |
|
2012-02-28 19:23:02 |
Scott Moser |
cloud-utils: importance |
Undecided |
High |
|
2012-02-28 19:23:02 |
Scott Moser |
cloud-utils: status |
New |
Fix Committed |
|
2012-02-28 19:23:02 |
Scott Moser |
cloud-utils: assignee |
|
Scott Moser (smoser) |
|
2012-02-28 19:23:14 |
Scott Moser |
cloud-initramfs-tools (Ubuntu): importance |
Undecided |
High |
|
2012-02-28 19:23:14 |
Scott Moser |
cloud-initramfs-tools (Ubuntu): status |
In Progress |
Fix Released |
|
2012-02-28 19:23:31 |
Scott Moser |
cloud-utils (Ubuntu): importance |
Undecided |
High |
|
2012-02-28 19:23:31 |
Scott Moser |
cloud-utils (Ubuntu): status |
New |
In Progress |
|
2012-02-28 19:23:31 |
Scott Moser |
cloud-utils (Ubuntu): milestone |
|
ubuntu-12.04-beta-1 |
|
2012-02-28 19:23:31 |
Scott Moser |
cloud-utils (Ubuntu): assignee |
|
Scott Moser (smoser) |
|
2012-02-28 19:35:38 |
Scott Moser |
description |
Not a dupe of bug 906722, but it seems very similar.
Occasionally on openstack clouds, we're seeing the root partition not being/grown on first-boot as it should be.
This was reported, and I have observed it on precise alpha-2 and will attach console logs. It happens sporadically.
The output of the relevant section of initramfs in the failed case looks like this:
| Begin: Running /scripts/init-premount ... done.
| Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
| Begin: Running /scripts/local-premount ... done.
| [ 0.940836] EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null)
| Begin: Running /scripts/local-bottom ... [ 0.955771] FDC 0 is a S82078B
| [ 1.012874] vda: vda1
| GROWROOT: WARNING: resize failed: FAILED: failed to resize
| ***** WARNING: Resize failed, attempting to revert ******
| Re-reading the partition table ...
| BLKRRPART: Device or resource busy
| The command to re-read the partition table failed.
| Run partprobe(8), kpartx(8) or reboot your system now,
| before using mkfs
| ***** Appears to have gone OK ****
| [ 1.114017] EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null)
| done.
| done.
| Begin: Running /scripts/init-bottom ... done.
In the successful case, it looks like this:
| Begin: Running /scripts/init-premount ... done.
| Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
| Begin: Running /scripts/local-premount ... done.
| [ 1.035664] EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null)
| Begin: Running /scripts/local-bottom ... [ 1.052365] FDC 0 is a S82078B
| [ 1.094201] vda: vda1
| [ 1.135831] vda: vda1
| GROWROOT: CHANGED: partition=1 start=16065 old: size=4176900 end=4192965 new: size=20948760,end=20964825
| [ 1.164067] Refined TSC clocksource calibration: 2532.595 MHz.
| [ 1.202383] EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null)
| done.
| done.
| Begin: Running /scripts/init-bottom ... done.
The code that is running here is growroot/scripts/local-bottom/growroot [1], growpart is part of cloud-utils [2].
Other relevant info, in at least one case, a reboot got the partition resized.
--
[1] http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/cloud-initramfs-tools/precise/view/head:/growroot/scripts/local-bottom/growroot
[2] http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/cloud-utils/precise/view/head:/bin/growpart |
Not a dupe of bug 906722, but it seems very similar.
Occasionally on openstack clouds, we're seeing the root partition not being/grown on first-boot as it should be.
This was reported, and I have observed it on precise alpha-2 and will attach console logs. It happens sporadically.
The output of the relevant section of initramfs in the failed case looks like this:
| Begin: Running /scripts/init-premount ... done.
| Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
| Begin: Running /scripts/local-premount ... done.
| [ 0.940836] EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null)
| Begin: Running /scripts/local-bottom ... [ 0.955771] FDC 0 is a S82078B
| [ 1.012874] vda: vda1
| GROWROOT: WARNING: resize failed: FAILED: failed to resize
| ***** WARNING: Resize failed, attempting to revert ******
| Re-reading the partition table ...
| BLKRRPART: Device or resource busy
| The command to re-read the partition table failed.
| Run partprobe(8), kpartx(8) or reboot your system now,
| before using mkfs
| ***** Appears to have gone OK ****
| [ 1.114017] EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null)
| done.
| done.
| Begin: Running /scripts/init-bottom ... done.
In the successful case, it looks like this:
| Begin: Running /scripts/init-premount ... done.
| Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
| Begin: Running /scripts/local-premount ... done.
| [ 1.035664] EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null)
| Begin: Running /scripts/local-bottom ... [ 1.052365] FDC 0 is a S82078B
| [ 1.094201] vda: vda1
| [ 1.135831] vda: vda1
| GROWROOT: CHANGED: partition=1 start=16065 old: size=4176900 end=4192965 new: size=20948760,end=20964825
| [ 1.164067] Refined TSC clocksource calibration: 2532.595 MHz.
| [ 1.202383] EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null)
| done.
| done.
| Begin: Running /scripts/init-bottom ... done.
The code that is running here is growroot/scripts/local-bottom/growroot [1], growpart is part of cloud-utils [2].
Other relevant info, in at least one case, a reboot got the partition resized.
--
[1] http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/cloud-initramfs-tools/precise/view/head:/growroot/scripts/local-bottom/growroot
[2] http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/cloud-utils/precise/view/head:/bin/growpart
Related bugs:
* bug 942788: sfdisk without --no-reread is likely to cause race conditions |
|
2012-02-29 01:38:24 |
Launchpad Janitor |
cloud-utils (Ubuntu): status |
In Progress |
Fix Released |
|
2012-02-29 02:07:17 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/cloud-utils |
|
2012-03-05 15:59:33 |
James Troup |
tags |
|
canonistack |
|
2012-10-01 19:15:48 |
Scott Moser |
cloud-utils: status |
Fix Committed |
Fix Released |
|