e9857d616d
This patch is part of the docs migration for Cinder. It is more or less a drag and drop of the docs from openstack-manuals admin-guide directory. I needed to change some syntax to work with Cinder's more stringent doc build. Note that the purpose of this patch is just to get the documentation back to an accessible location. Later patches will clean up the organization and content. Change-Id: Ib3f9255e0f9f2ff42a0ee4126607ff319a3d901e
1.1 KiB
Gracefully remove a GlusterFS volume from usage
Configuring the cinder volume service to use GlusterFS
involves creating a shares file (for example,
/etc/cinder/glusterfs). This shares file lists each
GlusterFS volume (with its corresponding storage server) that the
cinder volume service can use for back end storage.
To remove a GlusterFS volume from usage as a back end, delete the volume's corresponding entry from the shares file. After doing so, restart the Block Storage services.
Restarting the Block Storage services will prevent the
cinder volume service from exporting the deleted GlusterFS
volume. This will prevent any instances from mounting the volume from
that point onwards.
However, the removed GlusterFS volume might still be mounted on an instance at this point. Typically, this is the case when the volume was already mounted while its entry was deleted from the shares file. Whenever this occurs, you will have to unmount the volume as normal after the Block Storage services are restarted.