i did a storage migration from local lvm to ceph. all went fine. but after the next start of windows i had a lot of corrupt files when rebooting the windows server (windows 2008)
Hi,...
both vms where i did the disk move have big inconsistencies and needed a filedisk check...
Hi,cache: none
[COLOR=#008800][FONT=monospace]+ /* s->common.offset contains the number of bytes already processed so[/FONT][/COLOR]
[COLOR=#008800][FONT=monospace]+ * far, cnt is the number of dirty sectors remaining and[/FONT][/COLOR]
[COLOR=#008800][FONT=monospace]+ * s->sectors_in_flight is the number of sectors currently being[/FONT][/COLOR]
[COLOR=#008800][FONT=monospace]+ * processed; together those are the current total operation length */[/FONT][/COLOR]
[COLOR=#008800][FONT=monospace]+ s->common.len = s->common.offset +[/FONT][/COLOR]
[COLOR=#008800][FONT=monospace]+ (cnt + s->sectors_in_flight) * BDRV_SECTOR_SIZE;[/FONT][/COLOR]
thank you.
i will install some machines on my test environment and try to install the new qemu verion. still i also first have to reproduce the bug in the storage migration form the production cluster in the test environment. i am not 100% sure if every time i transfered a machine to the cluster it happened. at least before migrating the 2 windows machines i migrated 2 linux machines and they seem to work normally and did not want to make some filecheck on reboot etc...
i will start to test ....
hmmm ok. ceph has the discard/trimming feature of qemu?
also currently drive-mirroring allocate all blocks (including zeros block),so no sparse on target. this will be fixed in qemu 2.4.