HP MSA 1040 HP MSA 1040 SMU Reference Guide (762784-001, March 2014) - Page 55

Changing a vdisk’s name, Configuring drive spin down for a vdisk

Page 55 highlights

Changing a vdisk's name To change a vdisk's name 1. In the Configuration View panel, right-click a vdisk and select Configuration > Modify Vdisk Name. The main panel shows the vdisk's name. 2. Enter a new name. A vdisk name is case sensitive; cannot already exist in the system; and cannot include a comma, double quote, angle bracket, or backslash. The name you enter can have a maximum of 32 bytes. 3. Click Modify Name. The new name appears in the Configuration View panel. Changing a vdisk's owner Each vdisk is owned by one of the controllers, A or B, known as the preferred owner. Typically, you should not need to change vdisk ownership. When a controller fails, the partner controller assumes temporary ownership of the failed controller's vdisks and resources, becoming the current owner. If the system uses a fault-tolerant cabling configuration, both controllers' LUNs are accessible through the partner. CAUTION: • Before changing the owning controller for a vdisk, you must stop host I/O to the vdisk's volumes. • Because a volume and its snap pool must be in vdisks owned by the same controller, if an ownership change will cause volumes and their snap pools to be owned by different controllers, the volumes will not be able to access their snap pools. Changing the owner of a vdisk does not affect the mappings volumes in that vdisk. To change a vdisk's owner 1. In the Configuration View panel, right-click a vdisk and select Configuration > Modify Vdisk Owner. The main panel shows the vdisk's owner. 2. Select a new owner. 3. Click Modify Owner. A confirmation dialog appears. 4. Click Yes to continue; otherwise, click No. If you clicked Yes, a processing dialog appears. When processing is complete a success dialog appears. 5. Click OK. Configuring drive spin down for a vdisk The drive spin down (DSD) feature monitors disk activity within system enclosures and spins down inactive disks to conserve energy. For a specific vdisk, you can enable or disable DSD and set the period of inactivity after which the vdisk's disks and dedicated spares automatically spin down. To configure a time period to suspend and resume DSD for all vdisks, see "Scheduling drive spin down for all disks" (page 50). To configure DSD for available disks and global spares, see "Configuring drive spin down for available disks and global spares" (page 49). DSD affects disk operations as follows: • Spun-down disks are not polled for SMART events. • Operations requiring access to disks may be delayed while the disks are spinning back up. • If a suspend period is configured and it starts while a vdisk has started spinning down, the vdisk spins up again. Configuring drive spin down for a vdisk 55

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190

Configuring drive spin down for a vdisk
55
Changing a vdisk’s name
To change a vdisk’s name
1.
In the Configuration View panel, right-click a vdisk and select
Configuration > Modify Vdisk Name
. The main
panel shows the vdisk’s name.
2.
Enter a new name. A vdisk name is case sensitive; cannot already exist in the system; and cannot include a
comma, double quote, angle bracket, or backslash. The name you enter can have a maximum of 32 bytes.
3.
Click
Modify Name
. The new name appears in the Configuration View panel.
Changing a vdisk’s owner
Each vdisk is owned by one of the controllers, A or B, known as the
preferred owner
. Typically, you should not need
to change vdisk ownership.
When a controller fails, the partner controller assumes temporary ownership of the failed controller’s vdisks and
resources, becoming the
current owner
. If the system uses a fault-tolerant cabling configuration, both controllers’ LUNs
are accessible through the partner.
CAUTION:
Before changing the owning controller for a vdisk, you must stop host I/O to the vdisk’s volumes.
Because a volume and its snap pool must be in vdisks owned by the same controller, if an ownership change will
cause volumes and their snap pools to be owned by different controllers, the volumes will not be able to access
their snap pools.
Changing the owner of a vdisk does not affect the mappings volumes in that vdisk.
To change a vdisk’s owner
1.
In the Configuration View panel, right-click a vdisk and select
Configuration > Modify Vdisk Owner
. The main
panel shows the vdisk’s owner.
2.
Select a new owner.
3.
Click
Modify Owner
. A confirmation dialog appears.
4.
Click
Yes
to continue; otherwise, click
No
. If you clicked Yes, a processing dialog appears. When processing is
complete a success dialog appears.
5.
Click
OK
.
Configuring drive spin down for a vdisk
The drive spin down (DSD) feature monitors disk activity within system enclosures and spins down inactive disks to
conserve energy. For a specific vdisk, you can enable or disable DSD and set the period of inactivity after which the
vdisk’s disks and dedicated spares automatically spin down.
To configure a time period to suspend and resume DSD for all vdisks, see
"Scheduling drive spin down for all disks"
(page 50)
. To configure DSD for available disks and global spares, see
"Configuring drive spin down for available
disks and global spares" (page 49)
.
DSD affects disk operations as follows:
Spun-down disks are not polled for SMART events.
Operations requiring access to disks may be delayed while the disks are spinning back up.
If a suspend period is configured and it starts while a vdisk has started spinning down, the vdisk spins up again.