Does restoring a volume online make any logical sense? Generally operating systems don't like it when a mounted volume changes contents, and a restore, being a slow sequential write is likely to be even worse. Since you have to unmount anyway, attaching a new volume should not be an issue. Just because a feature is technically possible doesn't mean it is a good idea, particularly when the use of that feature under normal circumstances causes data corruption. We have plenty of code paths in cinder already that are hard to exercise fully and buggy (e.g migration) without adding more. On 10 Aug 2015 10:49, "hao wang" <sxmatch1986 at gmail.com> wrote: > Sorry if I missed something, since now we have supported backup in-use > volumes in L, so I wonder is there some plan or design to support > restoring on-line volumes. > > Thanks. > > -- > > Best Wishes For You! > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150810/49709b15/attachment.html>