On Thu, Dec 18, 2014 at 1:21 PM, Robert LeBlanc <robert@xxxxxxxxxxxxx> wrote: > Before we base thousands of VM image clones off of one or more snapshots, I > want to test what happens when the snapshot becomes corrupted. I don't > believe the snapshot will become corrupted through client access to the > snapshot, but some weird issue with PGs being lost or forced to be lost, > solar flares or alien invasions. > > My initial thought was to export a snapshot image and import it over the top > of the existing snapshot so that children would be preserved. No such luck. > I was hoping there would be a "i-really-really-want-to-do-this" option that > would let me restore the snapshot. I don't get it. This is to try and corrupt the snapshot? To repair it in the failure case? > Am I going about this the wrong way? I can see having to restore a number of > VM because of corrupted clone, but I'd hate to lose all the clones because > of corruption in the snapshot. I would be happy if the restored snapshot > would be flattened if it was a clone of another image previously. I don't remember exactly what metadata is stored how, that's related to this. I believe all the RBD images references are via a GUID that's distinct from the image name, which would make this non-trivial. It might be easier to upload the snapshot into a new rbd image and then change the headers on the children to point at the new image as the parent, but I don't think there's any easy tooling to allow that. The RBD guys would know better. -Greg _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |