Follow

Creating a file system for the volume

 

  1. Select a volume that has no mappings:

    prod-linux1-vol-20140702-1400 dm-5 - 9.00 12 3
  2. Run:

    infinihost volume create-filesystem dm-5

    The result is:

    Creating filesystem ... OK

Mounting a volume

Set a mount point to a volume that has a file system.

  1. Run the command with the following arguments:
    • Volume name
    • Mount point
infinihost volume mount dm-4 /mnt --y

The output is:

Mounting filesystem ... OK

Unmounting a volume

Disconnect the volume from the file system.

  1. Run the command with the following arguments:
    • Volume name
infinihost volume unmount dm-4 /mnt --y

The output is:

Volume unmounted

Deleting a volume

Delete the volume.

  1. Run the command with the following arguments:
      • Volume name
infinihost volume delete dm-4 --y

The output is:

Volume deleted

Mapping a volume

Map a volume that was created on InfiniBox to the host, using Host PowerTools.

  1. Run the command with the following arguments:
      • Volume name
infinihost volume map vol-1 /mnt --y

The output is:

Volume "vol-1" (id 82255) successfully mapped
  • The volume is visible using 
infinihost volume list

Unmapping a volume

Unmap a volume to disconnect it from the host. The volume remains on InfiniBox and can be connected to the host, or to other hosts.

This command accepts the device name or the mount point as an input (and does not accept the name of the volume as it is seen on InfiniBox).

  1. Run the command with the following arguments:
      • Volume name
infinihost volume unmap vol-1 --y

The output is:

Volume "vol-1" (id 82255) successfully unmapped

Speed testing the volume

The output of the command specifies:

  • Performance test results:
  • Path # 
  • HCTL -- an identifier of the host, channel, target and LUN 
  • Initiator WWN 
  • Target WWN 
  • NodeID 
  • PortID
  • Average throughput and average IOPS:

Instructions

Run:

infinihost volume speedtest dm-4 --duration=20

The output is:

Running performance test on /dev/mapper/mpathbm


Device paths:

Path #   
HCTL      Initiator WWN     Target WWN        NodeID 
PortID

Path #1   2:0:2:1   10000000c9b07494  5742b0f000040818  1      
8

Path #2   2:0:3:1   10000000c9b07494  5742b0f000040816  1      
6

Path #3   2:0:4:1   10000000c9b07494  5742b0f000040813  1      
3

Path #4   2:0:5:1   10000000c9b07494  5742b0f000040811  1      
1

Path #5   2:0:6:1   10000000c9b07494  5742b0f000040838  3      
8

Path #6   2:0:7:1   10000000c9b07494  5742b0f000040836  3      
6

Path #7   2:0:8:1   10000000c9b07494  5742b0f000040833  3      
3

Path #8   2:0:9:1   10000000c9b07494  5742b0f000040831  3      
1

Path #9   2:0:10:1  10000000c9b07494  5742b0f000040828  2      
8

Path #10  2:0:11:1  10000000c9b07494  5742b0f000040821  2      
1

Path #11  2:0:12:1  10000000c9b07494  5742b0f000040823  2      
3

Path #12  2:0:13:1  10000000c9b07494  5742b0f000040826  2      
6


Setting up...


Running for 20 seconds...


....................


          Average
Throughput  Average IOPS (0.5*MiB)


Total     1525*MB/s           2910

Path #1   137*MB/s            167

Path #2   137*MB/s            167

Path #3   139*MB/s            169

Path #4   139*MB/s            170

Path #5   139*MB/s            170

Path #6   138*MB/s            170

Path #7   140*MB/s            170

Path #8   138*MB/s            170

Path #9   137*MB/s            167

Path #10  137*MB/s            167

Path #11  137*MB/s            167

Path #12  137*MB/s            167


Average throughput is 177.62% of wire speed (8*Gib)

Paths are balanced

 



 


Comments

Powered by Zendesk