Hi Matias, As discussed, here you have the patch reconstructing the state for 1.2 devices. As mentioned in the patch itself, we make a tradeoff by doing this, as writes might fail (or be more unstable) in case that a block has been erased long before it is in used, and 1.2 does not have a way to communicate this. The only thing the device can do is force an erase on write when this happens, but if the device is responsible for this, one could argue that it could prevent double-erases - which follows better the predictability model we seek in Open-Channel. Thoughts? If we go this way, I will push a patch to the qemu 1.2 branch, as in the initialization, we need to match empty page reporting with the block metadata representing that the block is indeed erased. Ping me if you want this patch in advance for testing. Thanks, Javier Javier González (1): lightnvm: pblk: recover chunk state on 1.2 devices drivers/lightnvm/pblk-init.c | 138 ++++++++++++++++++++++++++++++++++++++----- 1 file changed, 124 insertions(+), 14 deletions(-) -- 2.7.4
