Hi, On Thu, 15 Nov 2018 at 06:57, Mousumi Mullick <mousumi.mullick@xxxxxxxxx> wrote: > > I am planning to run fio on a dozens of virtual machines across > multiple physical hosts and at some point will power off a physical > host. As fio workload is running I will be triggering random VM > migrations across a set of physical hosts. Since powering off a > physical host will abruptly power off all VMs running on that host, > none of the fio processes in them will have a verify_state file saved. > > Given this test, I was wondering if there is a way for fio to > continuously save verify_state to a file so that I can use it > unconditionally on a subsequent power on to verify the data written so > far? Why not create a trigger file (see https://fio.readthedocs.io/en/latest/fio_doc.html#cmdoption-trigger-file , https://fio.readthedocs.io/en/latest/fio_doc.html#verification-and-triggers ) to let fio know it needs to do a state save (it will also exit itself)? You may even be able to arrange for fio to send a command that powers the host off if you're using the client/server model with the appropriate trigger type. Further, don't you need to know fio has finished doing the state save correctly (note the that the trigger file will be deleted when fio is done with it)? If you power off a VM halfway through fio saving its state you risk generating/getting an incomplete/corrupt state file... -- Sitsofe | http://sucs.org/~sits/
