Description of problem:
If a VDO volume is stopped, and has its backing device resized offline, the message for the physical block count change will print what should be "Physical block count was <old_size>, now <new_size>", but it was discovered in BZ 1582647 that the message now prints as "Physical block count was <new_size>, now <new_size>".

(This does not occur with a backing device that is resized offline)

Version-Release number of selected component (if applicable):
kmod-kvdo-6.1.1.99-1.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Create a partition on a test device, with ample space for resizing (I used a 50 GiB partition).
2. Create a VDO volume on the test partition.
3. Stop the VDO volume with the "vdo stop" command.
4. Grow the device.
5. Start the VDO volume with the "vdo start" command.
6. Execute a "vdo growPhysical" command.



Actual results:
The growPhysical command executes successfully, but the message printed has an "old size" listed with the value of the new size.

Example: "kvdo7:dmsetup: Physical block count was 26214144, now 26214144"


Expected results:
The growPhysical command executed successfully, and the message indicates the previous physical block count, and the new physical block count after the growPhysical operation.

Example: "kvdo7:dmsetup: Physical block count was 13106944, now 26214144"


Additional info:

Demonstration on a test system:

[root@localhost ~]# parted /dev/nvme0n1 mkpart pri 1MiB 50GiB     
Information: You may need to update /etc/fstab.

[root@localhost ~]# vdo create --name=vdo1 --device=/dev/nvme0n1p1
Creating VDO vdo1
Starting VDO vdo1
Starting compression on VDO vdo1
VDO instance 6 volume is ready at /dev/mapper/vdo1
[root@localhost ~]# vdostats vdo1 --verbose | grep hysical\ blocks
  physical blocks                     : 13106944
[root@localhost ~]# vdo stop --name=vdo1
Stopping VDO vdo1
[root@localhost ~]# parted /dev/nvme0n1 resizepart 1 100GiB
Information: You may need to update /etc/fstab.

[root@localhost ~]# vdo start --name=vdo1                                 
Starting VDO vdo1
Starting compression on VDO vdo1
VDO instance 7 volume is ready at /dev/mapper/vdo1
[root@localhost ~]# vdostats vdo1 --verbose | grep hysical\ blocks
  physical blocks                     : 13106944
[root@localhost ~]# date; vdo growPhysical --name=vdo1
Tue Jul  3 16:10:40 EDT 2018
[root@localhost ~]# vdostats vdo1 --verbose | grep hysical\ blocks
  physical blocks                     : 26214144

Jul  3 16:10:40 localhost kernel: kvdo7:dmsetup: Preparing to resize physical to 26214144
Jul  3 16:10:40 localhost kernel: kvdo7:dmsetup: Done preparing to resize physical
Jul  3 16:10:40 localhost kernel: kvdo7:dmsetup: suspending device 'vdo1'
Jul  3 16:10:40 localhost kernel: kvdo7:dmsetup: device 'vdo1' suspended
Jul  3 16:10:40 localhost kernel: kvdo7:dmsetup: Physical block count was 26214144, now 26214144
Jul  3 16:10:40 localhost kernel: kvdo7:dmsetup: resuming device 'vdo1'
Jul  3 16:10:40 localhost kernel: kvdo7:dmsetup: device 'vdo1' resumed