Block Storage - Documents

• Service introduction
• Support information

Known Issues

• Status after Edit Volume of Block Storage remains “Updating”

FAQ

• When I try to create a volume of Block Storage / File Storage, “error_creating/Cluster does not have a capacity” has been displayed in the status field of the volume.Block storage (IO performance ensure), ECL2.0, File Storage, File Storage Premium, File Storage Standard / Construction

  The cause might be one of following issues.

  1. The menu is not provided in that region or group.

  Please refer to below for the list of services provided in each region or group. Service Descriptions – The List of Services provided in each Region

  2. Creating a volume is not available temporarily.

  (1) Please try it again later.

  (2) Please consider creating a volume in another region / another group.

  (3) When the issue is not resolved by the above actions, due to popular demand, we are afraid that it might not be possible to do resource creation in the region / group where the customer is trying to do it. In that case, please create a ticket via Ticket System.

  Is this page helpful?

  Yes No

  Open in a new window
• An error “Create-port-failed” occurred when creating a block storage volume.Block storage (IO performance ensure), ECL2.0 / Construction, Specification

  Volume creation may have failed due to the narrow range of the IP address pool set for virtual storage. Please extend the IP address pool range, create virtual storage again, and try creating a volume.
  # You cannot extend the IP address pool range from “Edit Virtual Storage”

  Reference: Tutorials – Block Storage – How to Create a Block Storage (Provisioned I/O Performance)

  Is this page helpful?

  Yes No

  Open in a new window
• Multi-path connection from the Linux server to the block storage volume is made, but the timeout value of the iSCSI initiator can not be changed from the iscsiadm command.Block storage (IO performance ensure), ECL2.0 / Operation, Specification

  It may be caused by the kernel specification of the Linux OS. Please check the kernel version you are using and if it corresponds to the version described in [Cause] below, please change the timeout value of iSCSI initiator in the procedure described in [How to change the setting] below.

  Cause

  In iSCSI + DM-Multipath environment, the default value (5) of “fast_io_fail_tmo” parameter in /etc/multipath.conf is set to the recovery_tmo variable held by the kernel.

  This recovery_tmo variable is the same as used for setting replacement_timeout with iscsiadm, but it has been modified from the specific kernel, not overwriting the value by iSCSI side.

  For this reason, even if you change the value with iscsiadm, the default setting on the multipath side becomes effective so, as a result, the value can not be changed.

  The kernel that has been modified so that the value is not overwritten by the iSCSI side operation is as follows.

  RHEL7.1(3.10.0-229.20.1.el7)
  RHEL7.2(3.10.0-327.el7)

  How to change the settings

  Permanent settings

  Put the configuration of either of the followings in “/etc/multipath.conf”.

  1. fast_io_fail_tmo 120 (This value is reflected to recovery_tmo)

  – Put “fast_io_fail_tmo 120” in defaults section of “/etc/multipath.conf”.

  – Restart multipathd.

  2. fast_io_fail_tmo off (The valur ofreplacement_timeout(120) is reflected to recovery_tmo)

  – Put “fast_io_fail_tmo off” in defaults section of “/etc/multipath.conf”.

  – Restart multipathd.

  – Change “replacement_timeout”.

  – Logout / login iscsi session.

  * Restarting multipathd is safe even during I/O processing.

  Provisional settings

  Change “recovery_tmo” of the corresponding sysfs.
  ex.
  # echo “120” > /sys/class/iscsi_session/session1/recovery_tmo
  # echo “120” > /sys/class/iscsi_session/session2/recovery_tmo

  Is this page helpful?

  Yes No

  Open in a new window
• Is the storage redundant?Block storage (IO performance ensure), ECL2.0, File Storage Premium, File Storage Standard / Specification

  The storage facilities are redundant.

  The storage facility group concept allows customers to use different groups to ensure physical equipment redundancy.

  For the group of the storage menu, refer to the following.

  Service Descriptions – Group in Storage Menu

   

  Is this page helpful?

  Yes No

  Open in a new window
• Can I create a group A volume and a group B volume in one virtual storage?Block storage (IO performance ensure), ECL2.0, File Storage Premium, File Storage Standard / Construction, Specification

  Yes. It is possible to select the group to be created for each volume.
  However, there are Groups that are not provided depending on the use region, so please check the services provided in each region of the service descriptions.

  Service Descriptions – 12. The List of Services provided in each Region.

   

  Is this page helpful?

  Yes No

  Open in a new window
• Please tell me about the iSCSI configuration of virtual server.Block storage (IO performance ensure), ECL2.0, Virtual Server / Operation

  Approximate one minute downtime is expected in case of logical network failure which provides the network to virtual server. (See [Service Descriptions – Support] for detail.)
  If you set up storage connection by using iSCSI from virtual server, please take account into the downtime.
  If you connect to our block storage service, please refer [Tutorials – Attaching resources to a Block Storage Volume].
  If you connect to the storage that we don’t provide, please contact your storage provider.

  The following shows some examples of configuration to hold I/O during the downtime.
  The impact to your application has to be tested and evaluated additionally for your system.

  The multipath devices can be used to make I/O queued at multipath layer in case of a disconnection to iSCSI target.
  For RHEL guest, the option of ‘features “1 queue_if_no_path”‘ makes I/Os held at multi-path layer when all paths are down.

  If the multipath devices are not used, the timeout of iSCSI layer needs to be set long enough.
  For RHEL guest, we set iSCSI initiator timeout to 120 seconds.

  Configuration file name: /etc/iscsi/iscsid.conf
  Parameter: node.session.timeo.replacement_timeout
  Value: 120 (Default value: 120)

  For Windows guest, we set both of disk I/O timeout and iSCSI initiator request timeout to 120 seconds.

  Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\disk
  Name: TimeoutValue
  Value: 120 (Default value: 60)

  Key: HKLM\SYSTEM\CurrentControlSet\Control\Class{4D36E97B-E325-11CE-BFC1-08002BE10318}\0000\Parameters (*1)
  Name: MaxRequestHoldTime
  Value: 120 (Default value: 60)
  (*1) The part of "0000" may vary. Please choose the instance number of Microsoft iSCSI Initiator.

  Is this page helpful?

  Yes No

  Open in a new window
• Can I create both Block Storage and File Storage on the same Logical Network?Block storage (IO performance ensure), ECL2.0, File Storage Premium, File Storage Standard / Construction, Specification

  No.
  You cannot create multiple virtual storages on one Logical Network.

  Reference:

  Service Descriptions – Block Storage (Provisioned I/O Performance) – Available Functions

  Service Descriptions – File Storage (Premium) – Available Functions

  Service Descriptions – File Storage (Standard) – Available Functions

  Is this page helpful?

  Yes No

  Open in a new window
• ACL, Kerberos or pNFS authentication are available on Block Storage menu?Block storage (IO performance ensure), ECL2.0 / Construction, Specification

  No. ACL, Kerberos or pNFS authentication are not available on Block Storage menu.
  Only IQN authentication is supported.

  Reference: Service Descriptions – Block Storage (Provisioned I/O Performance)

  Is this page helpful?

  Yes No

  Open in a new window
• When I create a volume of Block Storage, an error occurs “It is not a valid IQN.”Block storage (IO performance ensure), ECL2.0 / Construction, Specification

  You can use half size alphanumeric characters (letters are lower case only) in Initiator IQN.

  When there is any uppercase letter in Initiator IQN, an error occurs. Please re-set the Initiator IQN without uppercase letters.

  Tutorials – Block Storage – How to Create a Block Storage

  Is this page helpful?

  Yes No

  Open in a new window
• Please tell me the payout policy of the target IP address when creating volumes of Block Storage.Block storage (IO performance ensure), ECL2.0

  In Block Storage, as a rule, two IP addresses are paid out each time one volume is created for redundancy.

  If multiple Block Storage volumes are created, multiple volumes may use the same target IP address depending on the physical location of the volume at that point.

  * Volumes created in the same zone / group do not necessarily use the same target IP address.

  The target IP address is automatically determined at the time of volume creation and can not be specified by the customer.

  Even when the created multiple volumes use the same target IP address, since the volumes are logically divided, there is no particular impact on IO performance, such as a decrease in network bandwidth to existing volumes .

  Also, if the same target IP address is given, you can check which volume is used by checking the lun_id which is different for each volume on the details screen of the created volume.

  FAQ – Can I specify the target IP address when creating volume of Block Storage? Also, can I change it after creation?

  FAQ – When creating multiple volumes of Block Storage / File Storage, the same target IP address was given. Is it normal?

  FAQ – Can I specify multiple IP ranges for virtual storage IP address pool in Block Storage / File Storage service?

  Is this page helpful?

  Yes No

  Open in a new window