yahoo-eng-team team mailing list archive

[Harm Weites <harm@xxxxxxxxxx>]

Public bug reported:

Upon booting a new instance of Cirros 0.3.1, 0.3.2-pre1 or 0.3.2-pre2
the resize2fs command isn't run. Growroot did run, it's just the
filesystem that isn't resized. This instance is booting from a volume,
the platform is Openstack.

GROWROOT: CHANGED: partition=1 start=16065 old: size=64260 end=80325
new: size=6265350,end=6281415

And after reboot:
NOCHANGE: partition 1 is size 6265350. it cannot be grown

So partitions look to be just fine.

Cirros-per should have put down a marker in /var/lib/cirros/sem but for
some reason that didn't happen. Hacking a -v into
/etc/rc3.d/S55-resizefs shows it does try to run resize2fs:

using state_dir=/var/lib/cirros/sem, marker=once.once.resizefs
[once] sh -c o=/tmp/resize.out;

So somewhere along these lines it bails out:
cirros-per once resizefs -- \
                        sh -c 'o=/tmp/resize.out;
                                resize2fs -d 30 /dev/root >$o 2>&1 &&
                                rm -f $o && exit 0 ||
                                echo "resize failed!" 1>&2;
                                cat $o 1>&2; exit 1;' resizefs &

Contents of /tmp/resize.out only show the following:
resize2fs 1.42.2 (27-Mar-2012)

Manually running resize2fs does bring me a fullsized filesystem - but
thats not a solution.

** Affects: cirros
     Importance: Undecided
         Status: New

** Project changed: cloud-init => cirros

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1261710

Title:
  Filesystem not beeing resized

Status in CirrOS a tiny cloud guest:
  New

Bug description:
  Upon booting a new instance of Cirros 0.3.1, 0.3.2-pre1 or 0.3.2-pre2
  the resize2fs command isn't run. Growroot did run, it's just the
  filesystem that isn't resized. This instance is booting from a volume,
  the platform is Openstack.

  GROWROOT: CHANGED: partition=1 start=16065 old: size=64260 end=80325
  new: size=6265350,end=6281415

  And after reboot:
  NOCHANGE: partition 1 is size 6265350. it cannot be grown

  So partitions look to be just fine.

  Cirros-per should have put down a marker in /var/lib/cirros/sem but
  for some reason that didn't happen. Hacking a -v into
  /etc/rc3.d/S55-resizefs shows it does try to run resize2fs:

  using state_dir=/var/lib/cirros/sem, marker=once.once.resizefs
  [once] sh -c o=/tmp/resize.out;

  So somewhere along these lines it bails out:
  cirros-per once resizefs -- \
                          sh -c 'o=/tmp/resize.out;
                                  resize2fs -d 30 /dev/root >$o 2>&1 &&
                                  rm -f $o && exit 0 ||
                                  echo "resize failed!" 1>&2;
                                  cat $o 1>&2; exit 1;' resizefs &

  Contents of /tmp/resize.out only show the following:
  resize2fs 1.42.2 (27-Mar-2012)

  Manually running resize2fs does bring me a fullsized filesystem - but
  thats not a solution.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cirros/+bug/1261710/+subscriptions