Managing storage pools

During the life of a storage pool many things can happen: the pool could ran out of space, disks could fail, the network topology might change etc.

managing storage pools

To manage a storage pool click on the “Manage storage pool” link in the Storage page list.

  1. A drive is a volume allocated to an instance from this storage pool (not a physical disk)

  2. A shared drive is a drive that can be attached to multiple instances (eg: for VMWare)

Putting a storage pool in maintenance mode

The maintenance mode is used to block all subsequent provisioning on the respective pool but will not affect existing LUNs.

Depending the operation that the admin wants to do it might be required that all servers that use volumes from this storage system are shutdown.

To view disk less servers that are booted from this respective storage pools scroll to the bottom the storage pool’s page:

managing storage pools

The admin should contact all users of those servers and schedule the downtime.

Performing an emergency reboot of all connected servers

Sometimes, if the storage has suffered a long period of downtime, the servers will have gone into a ‘read-only’ mode meaning they will no longer be able to function normally and they will not be able to recover on their own. A quick fix to this is the “Hard reboot powered-on servers with iSCSI booting” which will reboot only affected servers on this storage pool.

Cleaning up unused templates

Drives are created with COW from existing drives but over time or after migrations templates will need to be deleted from the storage. They are regular volumes on the storage and can be deleted normally if there is no drive ‘derived’ from it. To check for this look for the Origin template ID field of a drive in the drives list.