strip_boot_from_image: use sfill instead of fstrim
fstrim relies on the underlying device supporting it and on our
instances we're on lvm devices. Since we're fstrim'ing a mounted
loopback the ability to call fstrim is inherited by the parent device.
Something has changed in the kernel (see bug) that stopped us from
making the trim call on the loopback partition.
sfill with these options should accomplish the same thing (single
write with all zeros) as well as cleaning up inode space.
TEST=signer full tests with this commit.
Signed-off-by: engeg <email@example.com>
Tested-by: George Engelbrecht <firstname.lastname@example.org>
Auto-Submit: George Engelbrecht <email@example.com>
Reviewed-by: Jason Clinton <firstname.lastname@example.org>
Reviewed-by: Jared Loucks <email@example.com>
Reviewed-by: Greg Edelston <firstname.lastname@example.org>
Commit-Queue: George Engelbrecht <email@example.com>
Commit-Queue: Greg Edelston <firstname.lastname@example.org>
1 file changed