We can replicate the corruption pretty much at will. The sequence of events to trigger it is:
Create an instance using a cloud image
Start a job running with the following command: "dd if=/dev/urandom of=/var/tmp/mjb.1 bs=4M count=1000"
Live migrate the instance using a command like: "nova live-migration --block-migrate <server-id> <target-hypervisor>"
Once the migration has finished, stop the dd job on the instance
do a "Hard reboot" of the instance
When the instance boots, file system corruption will be observed and it won't boot correctly
We can replicate the corruption pretty much at will. The sequence of events to trigger it is:
Create an instance using a cloud image hypervisor> "
Start a job running with the following command: "dd if=/dev/urandom of=/var/tmp/mjb.1 bs=4M count=1000"
Live migrate the instance using a command like: "nova live-migration --block-migrate <server-id> <target-
Once the migration has finished, stop the dd job on the instance
do a "Hard reboot" of the instance
When the instance boots, file system corruption will be observed and it won't boot correctly