[Bug 1292234] Re: qcow2 image corruption in trusty (qemu 1.7 and 2.0 candidate)
Serge Hallyn
1292234 at bugs.launchpad.net
Thu May 22 18:23:11 UTC 2014
I have a clean install of trusty on an intel laptop. I added the
following upstart job in the forhallyn-trusty-amd64.img root partition:
####################################################################
description "update and shutdown"
author "Serge Hallyn <serge.hallyn at ubuntu.com>"
start on runlevel [2345]
script
sleep 5s
apt-get update
DEBIAN_FRONTEND='noninteractive' apt-get -y dist-upgrade
sleep 5s
shutdown -h now
end script
####################################################################
Then on the host I run this script:
####################################################################
#!/bin/bash
cp orig-with-upstart/forhallyn-trusty-amd64.img .
virsh snapshot-create-as forhallyn-trusty-amd64 pristine "uvt snapshot"
virsh start forhallyn-trusty-amd64
sleep 20s
while [ 1 ]; do
virsh list | grep -q forhallyn || break
sleep 20s
done
# guest has updated. check the image file and fs here
qemu-img check forhallyn-trusty-amd64.img
if [ $? -ne 0 ]; then
echo "image check failed after shutdown"
exit 1
fi
qemu-nbd -c /dev/nbd0 forhallyn-trusty-amd64.img
fsck -a /dev/nbd0p1
if [ $? -ne 0 ]; then
echo "fs bad after shutdown"
qemu-nbd -d /dev/nbd0
exit 1
fi
qemu-nbd -d /dev/nbd0
# now tweak the snapshots
virsh snapshot-delete forhallyn-trusty-amd64 pristine --children
virsh snapshot-create-as forhallyn-trusty-amd64 pristine "uvt snapshot"
# and check the image file and fs again
qemu-img check forhallyn-trusty-amd64.img
if [ $? -ne 0 ]; then
echo "image check failed after snapshot remove/create"
exit 1
fi
qemu-nbd -c /dev/nbd0 forhallyn-trusty-amd64.img
fsck -a /dev/nbd0p1
if [ $? -ne 0 ]; then
echo "fs bad after snapshot remove/create"
qemu-nbd -d /dev/nbd0
exit 1
fi
qemu-nbd -d /dev/nbd0
# all seems well
exit 0
####################################################################
I'll run that in a loop and see if it fails after 10 tries.
If you see anything there that I am NOT doing which would help to reproduce,
please let me know.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1292234
Title:
qcow2 image corruption in trusty (qemu 1.7 and 2.0 candidate)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1292234/+subscriptions
More information about the Ubuntu-server-bugs
mailing list