Comment 8 for bug 906722

Revision history for this message
Scott Moser (smoser) wrote :

I've not yet confirmed, but looking at git commits to util-linux from 2.19.1 to 2.20.1 reveals this one:
https://github.com/karelzak/util-linux/commit/e82810c6cf3fe94d2cf70d485a59c411ccb601b3#fdisk/sfdisk.c

The disk is definitely busy when we try to rewrite the parttion table in the initramfs.
The reason it is not unmounted is get out in the common (other-than-first-boot) path when the disk is not going to be updated.

2 things to look at:
 - --no-reread flag
 - make growroot support writing "what would you do" output, which growroot in cloud-initramfs-tools would then use.
   if it said "nothing to do", then nothing done. Otherwise it would unmount disk, do what would have been done and then continue on.