Comment 13 for bug 937352

I've now uploaded some new images, with the improved growroot, and the output of a failed resize looks like this:

------
Begin: Running /scripts/local-bottom ... [ 0.892501] vda: vda1
GROWROOT: WARNING: resize failed: attempt to resize /dev/vda failed. sfdisk output below:
| Checking that no-one is using this disk right now ...
| OK
|
| Disk /dev/vda: 1305 cylinders, 255 heads, 63 sectors/track
| Old situation:
| Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
|
| Device Boot Start End #cyls #blocks Id System
| /dev/vda1 * 1 260 260 2088450 83 Linux
| /dev/vda2 0 - 0 0 0 Empty
| /dev/vda3 0 - 0 0 0 Empty
| /dev/vda4 0 - 0 0 0 Empty
| New situation:
| Units = sectors of 512 bytes, counting from 0
|
| Device Boot Start End #sectors Id System
| /dev/vda1 * 16065 20964824 20948760 83 Linux
| /dev/vda2 0 - 0 0 Empty
| /dev/vda3 0 - 0 0 Empty
| /dev/vda4 0 - 0 0 Empty
| Successfully wrote the new partition table
|
| 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
| If you created or changed a DOS partition, /dev/foo7, say, then use dd(1)
| to zero the first 512 bytes: dd if=/dev/zero of=/dev/foo7 bs=512 count=1
| (See fdisk(8).)
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.006837] EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null)
-------

So, growroot tried to resize, the resize failed (with BLKRRPART busy). Then it tried to re-set it back to the original, and that BLKRRPART failed also.

So something other than the mount has the block device open.