What with Easter and some client visits, I’ve not had a chance to report on the UKOUG BI & Performance Management day since it ran last week. I’ve got a day at home today before I fly off to Bucharest tomorrow, so here’s the highlights and a few photos.
This event was the first that Rittman […]
I noticed on the Oracle OLAP blog the other day that a new white paper on Cube Organized Materialized Views has been uploaded to OTN. If you’ve followed Pete and my postings on this new feature in Oracle 11g the white paper goes into a bit more detail on how it works, and in our […]
First step in creating a Mirrored volume (RAID 1) on HP-UX running on Integrity servers is to locate the SAS (Serial Attached SCSI) devices.
How to locate the device address for the SAS controller:
|
root@vmhost:/> ioscan -fnd sasd Class I H/W Path Driver S/W State H/W Type Description ==================================================================== escsi_ctlr 0 0/4/1/0 sasd CLAIMED INTERFACE HP PCI/PCI-X SAS MPT Adapter /dev/sasd0 |
For checking already existing RAID devices and and unused disk drives run sasmgr with query options:
|
root@vmhost:/> sasmgr get_info -D /dev/sasd0 -q raid Fri Mar 7 13:38:53 2008 ———- PHYSICAL DRIVES ———- LUN dsf SAS Address Enclosure Bay Size(MB) /dev/rdsk/c3t0d0 0×5000cca0001798e1 1 3 140014 /dev/rdsk/c3t1d0 0×5000cca0001798b5 1 4 140014 /dev/rdsk/c3t2d0 0×5000cca000186691 1 5 140014 /dev/rdsk/c3t3d0 0×5000cca000177ed9 1 6 140014 ———- LOGICAL DRIVE 7 ———- Raid Level : RAID 1 Volume sas address : 0×6b9717fb640ccbf Device Special File : /dev/rdsk/c3t4d0 Raid State : OPTIMAL Raid Status Flag : ENABLED Raid Size : 139898 Rebuild Rate : 0.00 % Rebuild Progress : 100.00 % Participating Physical Drive(s) : SAS Address Enc Bay Size(MB) Type State 0×5000cca0001799e5 1 7 140014 SECONDARY ONLINE 0×5000cca00014d561 1 8 140014 PRIMARY ONLINE |
These disks are unused:
/dev/rdsk/c3t0d0
/dev/rdsk/c3t1d0
/dev/rdsk/c3t2d0
/dev/rdsk/c3t3d0
Double check to verify these disks are not used by any volume groups. I am going to use disks in bay 4 and 5 to create a Logical drive using Mirroring (RAID1) because they are located in same row on the rx6600 server , that helps identifying disks in use.
|
root@vmhost:/> sasmgr add -D /dev/sasd0 -q raid -q level=1 -q size=139898 -q enc_bay=1:4.1:5 ERROR: Enclosure and Bay entry is not a valid entry for this HBA. |
You have to specify add argument to sasmgr command if you are creating a new Logical drive and -q is used as command qualifier, since I am going to create mirrored volume I have used raid and level 1. On my first try i missed the ( , ) between drive enclosure locations so I received an ERROR.
|
root@vmhost:/> sasmgr add -D /dev/sasd0 -q raid -q level=1 -q size=139898 -q enc_bay=1:4,1:5 |
© 2008 Blog Aggregator - Amardeep Sidhu | Entries (RSS) and Comments (RSS)
Powered by Wordpress, design by Web4 Sudoku, based on Pinkline by GPS Gazette