let's discuss defeaturing non-thinp snaps
Tony has done the heavy lifting to get support for thin-provisioned LVM
snapshots into the latest version of LVM.
Yay!
My question now is, can we remove support for snapshots of *non*-thinp
volumes? It's currently done via a dumb copy, and now that we had to go
back to a single-threaded server, this could block other targetd
requests for a long time, and generally is a poor experience.
Additionally, copy() is the only call that supports ASYNC mode (because
it's slow.) If we only enable thinp snaps, we can remove the ASYNC
special-case from the targetd API specification.
Thoughts?
If that's acceptable, well...
...can we got further out on a limb and talk about removing non-thinp LV
support altogether? This would further allow us to streamline our
documentation and test matrix.
Regards -- Andy