devicemapper-rs
devicemapper-rs copied to clipboard
We should have a consistent plan or understanding for how we suspend and resume devices
Currently, this really only happens in two places:
- We resume a device when we create it.
- When we reload a new table, we load the table into the inactive slot, we suspend the device, and then we resume the device which has the effect of loading the table into the active slot.
Do we need a more global approach? How can we be sure we're not losing data w/out a different kind of testing from what we are doing currently?