When loading an internal snapshot whose L1 table is smaller than the current L1
table, the size of the current L1 would be shrunk to the snapshot's L1 size in
memory, but not on disk. This lead to incorrect refcount updates and eventuelly
to image corruption.

Instead of writing the new L1 size to disk, this simply retains the bigger L1
size that is currently in use and makes sure that the unused part is zeroed.
Signed-off-by: NKevin Wolf <kwolf@redhat.com>
Tested-by: NPhilipp Hahn <hahn@univention.de>
Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>