d96b6dfba0
When extending an in-use volume, the volume will be extended but the target exposing the volume will still report the original size. The target needs to be updated to pick up the change, but since it is in-use the update must be forced. This can cause IO disruption if there is active IO to the target, however retries will cause the next attempt to succeed and there will just be a few second IO pause on the host while the target session is reestablished. Not ideal, but it does recover with minimal impact on the host. And operators probably shouldn't extend volumes without pausing active IO to the volume anyway. See bug report comments for more testing details. Marking this as partial as it only addresses the tgt target and further investigation is needed to see if the other target drivers need similar updates. Change-Id: I0f7b58751c6d8d05cad5b1b95c4e21c8b5d36692 Partial-bug: #1731984
Team and repository tags
CINDER
You have come across a storage service for an open cloud computing service. It has identified itself as Cinder. It was abstracted from the Nova project.
- Wiki: https://wiki.openstack.org/Cinder
- Developer docs: https://docs.openstack.org/cinder/latest/
Getting Started
If you'd like to run from the master branch, you can clone the git repo:
For developer information please see HACKING.rst
You can raise bugs here https://bugs.launchpad.net/cinder
Python client
https://git.openstack.org/cgit/openstack/python-cinderclient