Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Dell PowerStore Importing External Storage to PowerStore Guide

Linux-based hosts

The following restrictions apply during a non-disruptive import involving Linux-based hosts:

  • Change in user-friendly names of volumes being imported is not supported.
    NOTE:Any device policy or user-friendly name on source volume will not be applied to the destination volume after import.
  • The mpathpersist command fails to get PR information for volumes mapped to clusters after the import. Use sg_persist.
  • LUNs cannot be removed from the storage group.
  • UUID-based mount points with EQL MPIO are not supported.
  • Only Linear volume LVM is supported, other LVM types, like striped LVM, are not supported.
  • For LVMs, ensure that the option allow_changes_with_duplicate_pvs is enabled in /etc/lvm/lvm.conf. If this option is set to 0 (disabled), change it to 1 (enabled). Otherwise, imported logical volumes will not become active again after a host reboot if duplicate Port VLAN identifiers (PVIDs) are discovered.
  • The maximum length of the hostname must be within 56 characters.
  • After or during the import of a volume and after reboot, the mount command displays the destination mapper name instead of the source mapper name. The same destination mapper name is listed in the df -h output.
  • Before importing a volume, the mount point entry in /etc/fstab should have the "nofail" option to avoid boot failures on host reboots. For example: /dev/mapper/364842a249255967294824591aa6e1dac /mnt/364842a249255967294824591aa6e1dac ext3 acl,user_xattr,nofail 0 0
  • Import to a PowerStore cluster from a Linux host running Oracle ASM on Dell Compellent SC storage is allowed only when the Oracle configuration uses logical sector size for ASM disk groups. See Setting the Oracle ASM logical block size for more details.
  • The keyword blacklist and curly brace should appear in the same line for imports to be successful. For example, "blacklist { " in the /etc/multipath.conf file.
  • If the keyword blacklist and curly brace are not in the same line, import will fail. If not present already, modify the multipath.conf file manually to the "blacklist {" form.
  • If the multipath.conf file has blacklist keyword, such as product_blacklist, before the blacklist section, move that section after the blacklist section for imports to work successfully.
NOTE: Ensure that the disk space on the host is not filled to maximum capacity. Free disk space on the host is needed for import operations.

The following is a known behavior during import on Linux-based hosts:

  • After host reboot, during import of the volume, the mount point in /etc/fstab points to the source device mapper. However, output of the mount or df -h command displays the destination device mapper name.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\