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.
I've not yet confirmed, but looking at git commits to util-linux from 2.19.1 to 2.20.1 reveals this one: /github. com/karelzak/ util-linux/ commit/ e82810c6cf3fe94 d2cf70d485a59c4 11ccb601b3# fdisk/sfdisk. c
https:/
The disk is definitely busy when we try to rewrite the parttion table in the initramfs. than-first- boot) path when the disk is not going to be updated.
The reason it is not unmounted is get out in the common (other-
2 things to look at: -tools would then use.
- --no-reread flag
- make growroot support writing "what would you do" output, which growroot in cloud-initramfs
if it said "nothing to do", then nothing done. Otherwise it would unmount disk, do what would have been done and then continue on.