Block Storage FAQ

Why can I provision block and file storage with an Endurance 10 IOPS tier in some data centers and not in others?

The File storage Endurance type 10 IOPS/GB tier is only available in select data centers, with new data centers being added soon.  You can find a full list of upgraded data centers and available features here.

If I have non-encrypted Block storage provisioned in a data center that has been upgraded for encryption, can I encrypt my Block storage?

Block storage that is provisioned prior to a data center upgrade cannot be encrypted. New Block storage provisioned in upgraded data centers is automatically encrypted ; there is no encrypt setting to choose from, it’s automatic.. Data on non-encrypted storage in an upgraded data center can be encrypted by creating a new Block LUN, then copying the data to the new encrypted LUN with host-based migration. See this article for instructions on how to perform the migration.

How to verify if MPIO is configured correctly in *NIX OSes

To check if multipath is picking up the devices, only the NETAPP devices should show up and there should be two of them. 

root@server:~# multipath -l 3600a09803830304f3124457a45757067 dm-1 NETAPP,LUN C-Mode size=20G features='1 queue_if_no_path' hwhandler='0' wp=rw |-+- policy='round-robin 0' prio=-1 status=active | `- 6:0:0:101 sdd 8:48 active undef running `-+- policy='round-robin 0' prio=-1 status=enabled `- 7:0:0:101 sde 8:64 active undef running

Check that the disks are present, and there should be two disks with the same identifier, and a /dev/mapper listing of the same size with the same identifier. The /dev/mapper device is the one that multipath sets up:

root@server:~# fdisk -l | grep Disk Disk /dev/sda: 500.1 GB, 500107862016 bytes Disk identifier: 0x0009170d Disk /dev/sdc: 21.5 GB, 21474836480 bytes Disk identifier: 0x2b5072d1 Disk /dev/sdb: 21.5 GB, 21474836480 bytes Disk identifier: 0x2b5072d1 Disk /dev/mapper/3600a09803830304f3124457a45757066: 21.5 GB, 21474836480 bytes Disk identifier: 0x2b5072d1

If it is not correctly setup, it will look like this: 

No multipath output root@server:~# multipath -l root@server:~#

This will show the devices blacklisted:

root@server:~# multipath -l -v 3 | grep sd Feb 17 19:55:02 | sda: device node name blacklisted Feb 17 19:55:02 | sdb: device node name blacklisted Feb 17 19:55:02 | sdc: device node name blacklisted Feb 17 19:55:02 | sdd: device node name blacklisted Feb 17 19:55:02 | sde: device node name blacklisted

fdisk shows only the sd* devices, and no /dev/mapper

root@server:~# fdisk -l | grep Disk Disk /dev/sda: 500.1 GB, 500107862016 bytes Disk identifier: 0x0009170d Disk /dev/sdc: 21.5 GB, 21474836480 bytes Disk identifier: 0x2b5072d1 Disk /dev/sdb: 21.5 GB, 21474836480 bytes Disk identifier: 0x2b5072d1

To ensure a proper MPIO configuration, please refer to our KnowledgeLayer Article on setting this up from Start to Finish:

http://knowledgelayer.softlayer.com/procedure/accessing-block-storage-performance-storage-linux

How many volumes can I provision?

By default, you can provision a combined total of 250 block and file storage volumes.  Please contact your sales representative to increase your volumes.

How many instances can share the use of a provisioned Block Storage volume?

The default limit for number of authorizations per block volume is 8. Please contact your sales representative to increase the limit.

When provisioning Performance or Endurance Block/File Storage, are the allocated IOPS enforced by instance or by volume?

IOPS are enforced at the volume level. Said differently, two hosts connected to a volume with 6000 IOPS share that 6000 IOPS.

How are IOPS measured?

IOPS are measured based on a load profile of 16kb blocks with random 50% read and 50% writes. Workloads that differ from this profile may experience lower performance.

What happens if I use a smaller block size when measuring performance?

Maximum IOPS can still be obtained when using smaller block sizes, however throughput will be lower. For example; a volume with 6000 IOPS would have the following throughput at various block sizes:

  1. 16KB * 6000 IOPS == ~93.75 MB/sec
  2. 8KB * 6000 IOPS == ~46.88 MB/sec
  3. 4KB * 6000 IOPS == ~23.44 MB/sec
Does the volume need to be pre-warmed to achieve expected throughput?

There is no need for pre-warming. You will observe specified throughput immediately upon provisioning the volume.

Why can I provision block and file storage with an Endurance 10 IOPS tier in some data centers and not in others?

The Block and File Endurance storage type 10 IOPS/GB tier is only available in select data centers, with new data centers being added soon.  You can find a full list of upgraded data centers and available features here.

How can I tell which of my Block or File storage LUNs/volumes are encrypted?

When viewing your list of Block or File storage in the customer portal, you will see a lock icon to the right of LUN/volume name for those that are encrypted.

How do I know if I am provisioning Block or File storage in an upgraded data center?

When provisioning Block or File storage, all upgraded data centers will be denoted with an asterisk (*) in the order form and an indication that you will be provisioning storage with encryption. Once the storage is provisioned, you will see an icon in the storage list that shows that volume or volume as encrypted. All encrypted volumes and volumes are provisioned in upgraded data centers only. You can find a full list of upgraded data centers and available features here.