tree e81682b3c7fd811c7c698c51a4a71a1139b2bc26
parent 2637a86ac2018323f90625609263004d489a9156
author dahn <daan.hoogland@shapeblue.com> 1587664587 +0200
committer GitHub <noreply@github.com> 1587664587 +0200
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJeodbLCRBK7hj4Ov3rIwAAdHIIAJ9khke+2L7/eKdC/TCzF7O6
 juENUYKqSzSQ5k58NYEMB+wNemLmkF49aKNhW16UNkyJ1gLw5aYSrgUjtBM5n/Hs
 NOmqsLKSsmVWiqn5qNs6ALjo+YDACBCatTZlEjyP6Glst/xazSX9WN91TWMr3iRP
 rD2/glMjCpwPPQa/VUqf2ygjMDUs1M/ik8Yh7x+p/4dYn23l/ONrM+HuDPBzdIAk
 4J9AV5lUyQOnZlM8emYMLq6QFC+M1OHq226QlizsgbXK2hBMh94/L3Clc0cBCJHr
 +aAqQtykmrXGRt+FsXQzKCkpw3K7xqNjk4zECOcQ0OTxYWY6UUJXzWaEaHDHHAM=
 =THnk
 -----END PGP SIGNATURE-----
 

Volume migration (#4043)

* Update AncientDataMotionStrategy.java

fix When secondary storage usage is> 90%, VOLUME migration across primary storage will cause the migration to fail and lose VOLUME

* Update AncientDataMotionStrategy.java

Volume is migrated across Primary storage. If no secondary storage is available(Or used capacity> 90% ), the migration is canceled.
Before modification, if secondary storage cannot be found, copyVolumeBetweenPools return NUll

copyAsync considers answer = null to be a sign of successful task execution, so it deletes the VOLUME on the old primary storage. This is the root cause of data loss, because VOLUME did not perform the migration at all.

* code in comment removed

Co-authored-by: div8cn <35140268+div8cn@users.noreply.github.com>
Co-authored-by: Daan Hoogland <dahn@onecht.net>