Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1002348.1
Update Date:2011-03-18
Keywords:

Solution Type  Technical Instruction Sure

Solution  1002348.1 :   How and When to Change OPEN-V Device Geometry on Sun StorEdge[TM] 9990 and Sun StorEdge[TM] 9985  


Related Items
  • Sun Storage 9970 System
  •  
  • Sun Storage 9990 System
  •  
  • Sun Storage 9985 System
  •  
  • Sun Storage 9980 System
  •  
Related Categories
  • GCS>Sun Microsystems>Storage - Disk>Datacenter Disk
  •  

PreviouslyPublishedAs
203290


Description
How and When to Change OPEN-V Device Geometry on Sun StorEdge[TM] 9990 and Sun StorEdge[TM] 9985

The OPEN-V device emulation was introduced in the Sun StorEdge[TM] 9970 (SE9970) and Sun StorEdge[TM] 9980 (SE9980) products. The cache slot / track size for the new emulation was increased in comparison to other emulations,  from 48k to 64k.  (See <Document: 1012382.1> for more detailed information on Sun StorEdge[TM] 9900 device geometry, including performance implications). The default cache slot and track size for OPEN-V on Sun StorEdge[TM] 9990/Sun StorEdge[TM] 9985 was increased again to 256k. However, on the newest arrays, one has  the option of using the new, larger track/slot size, or presenting the older 64k geometry to attached hosts. This article discusses potential situations under which each OPEN-V option might be advantageous, and provides procedures for changing OPEN-V device geometry.



Steps to Follow
Please review the following steps.

The circumstances under which one might want to use the "older" OPEN-V device geometry on SE9990 or SE9985 may already be readily apparent to the reader.  For example, if the user wants to employ a host-based volume manager to mirror between different array architectures, it will be necessary to make the devices from each array appear to be exactly equivalent in size and geometry, and hence capable of being mirrored.  In this case one would want to take advantage of the 9990/85's capability to present the older (64k) OPEN-V device geometry.

Theoretically, cache hit rates with primarily small, random read workloads might be better with the smaller, 64k track/slot size also.  This is because the 9900 arrays always stage a minimum of 1 track of data into cache, regardless of how small the read request may be.  If an application does very random reads of 8k, for example, it may not be efficient to stage an entire 256k of data, but this is what will occur by default with OPEN-V on SE9990/85.

The author conducted testing of both types of OPEN-V device geometry available on SE9990/85.  Vdbench was used to compare performance of both types of OPEN-V geometry with a variety of workloads, including small random reads, small random and sequential writes, a mixture of small random reads with small sequential writes, large sequential reads, and so on.  Only one test was found in which either geometry had a significant performance advantage.

On a test of small (8k) sequential reads, the new 256k track/slot size had a modest advantage. With the default (256k) slot/track size, a multithreaded sequential read on four raw OPEN-V devices on four different parity groups obtained an average of 10829 I/O operations per second (IOPS) and 84.6 MB/second.  The same test on the same physical devices, now presented with the 64k slot/track size, obtained 8846 IOPs and 69.1 MB/second.  This result implies that the newer OPEN-V device geometry may be preferred for performance reasons, at least in data warehouse environments.

OPEN-V device geometry is configured either globally, via system option mode 313, or for specific host groups, via host group option mode 16.  At this writing, neither of these modes can be set by end users, but rather must be configured by authorized Sun field service representatives.  Instructions for setting OPEN-V device geometry are included in the Sun Internal-Use Only section, below.



Product
Sun StorageTek 9990 System
Sun StorageTek 9985 System
Sun StorageTek 9980 System
Sun StorageTek 9970 System
Sun StorageTek 9900V Series Array

Internal Comments
For Internal Sun use only.


Instructions for setting host group option mode 16 can be found
in Fab <Document: 1000384.1> Host groups with host group option
mode 16 set ON will have OPEN-Vs presented to them with a 64k
track/slot size.  If a customer wants the OPEN-V 64k
track/slot size to be set for all OPEN-Vs on the array, system
option mode 313 can be set ON using the following procedure:





  1. From the SVP enter a <CTRL><SHIFT>m.





  2. You will get a password box.  The password is "mode".





  3. The SVP will go from "View Mode" to "Mode Mode"





  4. Select the Install button.





  5. Select the Change Configuration button.





  6. Select the System Option button.





  7. Within System Option, there will now appear a "mode" button.
     Select that,  and you will get a screen with available
    bits to set for system options 0-512.





  8. Check mode 313, confirm and save the changes.





Note that Hitachi requires that attached hosts should be
powered off
when changing device
geometry settings.  With Solaris, a reboot (even a reboot --
-r) will not be sufficient to cause the host to rewrite the logical
device's volume table of contents (VTOC), meaning that the host
could be operating with stale device geometry.  Other
operating systems may vary in requirements for recognizing the
change in device geometry, which is why Hitachi has the universal
recommendation for host power cycle.


Under Solaris, the default VTOC for SE9990/85 OPEN-V will have
the following parameters.


# prtvtoc /dev/rdsk/c4t60060E8004275000000027500000006Bd0s2
* /dev/rdsk/c4t60060E8004275000000027500000006Bd0s2 partition map
*
* Dimensions:
* 512 bytes/sector
* 512 sectors/track
* 15 tracks/cylinder
*....7680 sectors/cylinder

With host group option mode 16 or system option mode 313 enabled
on SE9990/85, or on SE9970/80, the OPEN-V VTOC will appear as
follows:


# prtvtoc /dev/rdsk/c4t60060E80042750000000275000000081d0s2
* /dev/rdsk/c4t60060E80042750000000275000000081d0s2 partition map
*
* Dimensions:
* 512 bytes/sector
* 128 sectors/track
* 15 tracks/cylinder
*....1920 sectors/cylinder

If a host power cycle is not possible, the following method for
refreshing the OPEN-V VTOC on Solaris has been tested and found to
be effective. However all I/O to the device must be halted prior to
performing these operations.





  1. Invoke the format command with the -e option, e.g.  format
    -e. 





  2. Select the OPEN-V device to be relabeled.





  3. Select the  label  option of format.





  4. A prompt will appear requesting label type.  Select
     1  for EFI and respond  y  to the ready
    prompt.





  5. Select the  label  option again.





  6. This time, select  0  to choose the SMI label
    type.





  7. Take the default ( no ) response to the next two
    prompts, and and respond  y  to the ready prompt.





  8. Repeat steps 2-7 for each device that needs to be relabeled.





A sample of the relabeling described above is provided below,
including  verify  commands to illustrate how the VTOC
has been rewritten.


format> di 34
selecting c4t60060E80042750000000275000000018d0
[disk formatted]
format> verify

Primary label contents:

Volume name = < >
ascii name = <HITACHI-OPEN-V-SUN-5003 cyl 10443 alt 2 hd 15 sec 512>
pcyl = 10445
ncyl = 10443
acyl = 2
nhead = 15
nsect = 512
Part Tag Flag Cylinders Size Blocks
0 unassigned wm 0 - 10442 38.24GB (10443/0/0) 80202240
1 unassigned wu 0 0 (0/0/0) 0
2 backup wu 0 - 10442 38.24GB (10443/0/0) 80202240
3 unassigned wm 0 0 (0/0/0) 0
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 0 0 (0/0/0) 0
6 unassigned wm 0 0 (0/0/0) 0
7 unassigned wm 0 0 (0/0/0) 0

format> label
[0] SMI Label
[1] EFI Label
Specify Label type[0]: 1
Ready to label disk; continue Y
format> label
[0] SMI Label
[1] EFI Label
Specify Label type[1]: 0
Auto configuration via format.dat[no]
Auto configuration via generic SCSI-2[no]
Ready to label disk, continue Y

format> verify

Primary label contents:

Volume name = < >
ascii name = <HITACHI-OPEN-V-SUN-5005 cyl 41781 alt 2 hd 15 sec 128>
pcyl = 41783
ncyl = 41781
acyl = 2
nhead = 15
nsect = 128
Part Tag Flag Cylinders Size Blocks
0 root wm 0 - 136 128.44MB (137/0/0) 263040
1 swap wu 137 - 273 128.44MB (137/0/0) 263040
2 backup wu 0 - 41780 38.25GB (41781/0/0) 80219520
3 unassigned wm 0 0 (0/0/0) 0
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 0 0 (0/0/0) 0
6 usr wm 274 - 41780 38.00GB (41507/0/0) 79693440
7 unassigned wm 0 0 (0/0/0) 0

OPEN-V, HDS, SE99, track, slot, sector, block, Hitachi, device, geometry, LDEV, option, mode
Previously Published As
84423

Change History
Date: 2007-11-13
User Name: 7058
Action: Approved
Comment: Changed internal sunsolve2 reference in external section to sunsolve.sun.com
Version: 6
Date: 2007-11-13
User Name: 7058
Action: Update Started
Comment: Fix links
Version: 0
Date: 2007-05-25
User Name: 31620
Action: Approved
Comment: Verified Metadata - ok
Verified Keywords - ok
Verified still correct for audience - currently set to contract
Audience left at contract as per FvF at
http://kmo.central/howto/content/voyager-contributor-standards.html
Checked review date - currently set to 2007-07-27 (bit short, but OK)
Checked for TM - ok as presented
Publishing under the current publication rules of 18 Apr 2005:
Checked for the word normalized - not present
Version: 5




Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback