Search This Blog

Friday, December 13, 2013

touch: Changing the Time Stamps

The touch command changes these times and is used in the following manner:

# touch options expressions filename(s)

When touch is used without options or an expression, both times are set to the current time. The file is created if it doesn't exist.., but not overwritten if it does:

#touch note #Creates file if it doesn't exist

Various Options of Touch Command:
-a (touch -a) Update only the access time to current time
-c (touch -c) Don't create if the file doesn't exist
-d (touch -d) Set an arbitrary time for both times using free format human readable data string
-m (touch -m) Update only the modification time to current time
-r (touch -r) Update both file's times from a reference file
-t (touch -t) Set an arbitrary time for both time using stamp


If you want to check the file timestamp, you can do so with this command:

#stat file

[root@localhost indrajit]# stat abcd
  File: `abcd'
  Size: 0         Blocks: 0          IO Block: 4096   regular empty file
Device: 802h/2050d Inode: 281784      Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2013-04-15 22:40:00.000000000 -0700
Modify: 2013-04-15 22:40:00.000000000 -0700
Change: 2013-12-12 20:08:43.506978374 -0800


Now let's use the command on file abcd, but only after seen its initial time stamps:


[root@localhost indrajit]# ls -l abcd Modification Time
-rw-r--r--. 1 root root 0 Apr 15  2013 abcd
[root@localhost indrajit]# ls -lu abcd Access Time
-rw-r--r--. 1 root root 0 Apr 15  2013 abcd


With the -m (modification) option, you can alter the modificaiton time alone:

#touch abcd
#ls -l abcd
-rw-r--r--   1 root       sys              0 Dec 13 05:33 abcd
#touch -m 02281030 abcd;ls -l abcd
-rw-r--r--   1 root       sys              0 Feb 28  2013 abcd

The -a (access) option changes the access time:

#ls -lu abcd
-rw-r--r--   1 root       sys              0 Dec 13 05:33 abcd
#touch -a 01261650 abcd;ls -lu abcd
-rw-r--r--   1 root       sys              0 Jan 26  2013 abcd


-c option
If you use this option, touch won’t do anything at all if the file specified doesn't exist. Look:

#ls -l xyz
xyz not found
#touch -c xyz;ls -l xyz
xyz not found


-r option
This option might come in handy if you want to copy a timestamp from a file to another file. Like so:


#ls -l abcd abcd1
-rw-r--r--   1 root       sys              0 Feb 28  2013 abcd
-rw-r--r--   1 root       sys              0 Dec 13 05:41 abcd1
#touch -r abcd1 abcd;ls -l abcd
-rw-r--r--   1 root       sys              0 Dec 13 05:41 abcd


-d and –t options
Both (-d) and (-t) options do the same thing, which is setting the same arbitrary timestamps for access and modification times. The difference is that (-d) uses free format human readable date, this means that you can use “Sun, 29 Feb 2004 16:21:42? or “2004-02-29 16:21:42” or even “next Thursday”. This option is complex to fully describe it here. On the other hand (-t) uses a simple stamp that you are confined to use. The stamp is [[CC]YY]MMDDhhmm[.ss]. [CC] is for century and you may ignore it and ignore the seconds as well. If you ignore [CC] the command will substitute it depending on what you enter as year. If you specify the year with only two digits, then CC is 20 for years in the range (0~68) and 19 for years in (69~99).


#ls -l abcd
-rw-r--r--   1 root       sys              0 Dec 13 05:41 abcd
#touch -t 3404152240 abcd;ls -l abcd
-rw-r--r--   1 root       sys              0 Apr 15  2034 abcd
#touch -t 8804152240 abcd;ls -l abcd
-rw-r--r--   1 root       sys              0 Apr 15  1988 abcd

In the first command the file timestamps will be set to: 15th April 2034 10:40 PM. While the second command will set it to: 15th April 1988 which is in a different century. If no year is specified it will be set to the current year. Example:


#touch -t 04152240 abcd;ls -l abcd
-rw-r--r--   1 root       sys              0 Apr 15  2013 abcd



Sunday, November 10, 2013

vxfs fsadm: attempt to resize......failed with errno 28

When extending the filesystem online using fsadm command its failing with below error:

# fsadm -F vxfs -b 10240M /fs_test 
vxfs fsadm: /dev/vg00/rfstest is currently 5636096 sectors - size will be increased
vxfs fsadm: attempt to resize /dev/vg00/rfstest failed with errno 28 
vxfs fsadm:  Retry the operation after freeing up some space

Error number 28 means ENOSPC from /usr/include/sys/errno.h
#define ENOSPC          28      /* No space left on device      */


Why is the ENOSPC
error while running fsadm even though there is enough free space on the filesystem?
Solution
NOTE: If a file system is full, busy or too fragmented, the resize operation may fails.

Follow the below steps to extend the filesystem online using fsadm :
Checked and found filesystem is heavily fragmented. As it can be seen from the above output that there is no free extent of 8KB or above.

# fsadm -F vxfs -D -E /fs_test 

  Directory Fragmentation Report
             Dirs        Total      Immed    Immeds   Dirs to   Blocks to
             Searched    Blocks     Dirs     to Add   Reduce    Reduce
  total          2887      1996      2131         0         3          99

  Extent Fragmentation Report
        Total    Average      Average     Total
        Files    File Blks    # Extents   Free Blks
        47977          85           5     1513016
    blocks used for indirects: 26820
    % Free blocks in extents smaller than 64 blks: 100.00
    % Free blocks in extents smaller than  8 blks: 100.00
    % blks allocated to extents 64 blks or larger: 90.52
    Free Extents By Size
           1:     215670            2:     221005            4:     213834
           8:          0           16:          0           32:          0
          64:          0          128:          0          256:          0
         512:          0         1024:          0         2048:          0
        4096:          0         8192:          0        16384:          0
       32768:          0        65536:          0       131072:          0
      262144:          0       524288:          0      1048576:          0
     2097152:          0      4194304:          0      8388608:          0
    16777216:          0     33554432:          0     67108864:          0
   134217728:          0    268435456:          0    536870912:          0
  1073741824:          0   2147483648
Ran the defragmentation on the filesystem.

# fsadm -F vxfs -d -e /fs_test 
NOTE: Defragmentation can take long time depending on the degree of fragmentation, disk speed and number of inodes in the filesystem. In this case it took about 45 min. More information is available on man 1M fsadm_vxfs command.
Fragmentation report after defragmentation of filesystem:

# fsadm -F vxfs -D -E /fs_test 

  Directory Fragmentation Report
             Dirs        Total      Immed    Immeds   Dirs to   Blocks to
             Searched    Blocks     Dirs     to Add   Reduce    Reduce
  total          2887      1879      2131         0         2           5

  Extent Fragmentation Report
        Total    Average      Average     Total
        Files    File Blks    # Extents   Free Blks
        47977          84           1     1539889
    blocks used for indirects: 48
    % Free blocks in extents smaller than 64 blks: 4.94
    % Free blocks in extents smaller than  8 blks: 0.52
    % blks allocated to extents 64 blks or larger: 91.40
    Free Extents By Size
           1:       1029            2:       1144            4:       1165
           8:       1319           16:       1253           32:       1170
          64:       1023          128:        879          256:        611
         512:        388         1024:        171         2048:         89
        4096:         36         8192:         12        16384:          4
       32768:          4        65536:          0       131072:          1
      262144:          0       524288:          0      1048576:          0
     2097152:          0      4194304:          0      8388608:          0
    16777216:          0     33554432:          0     67108864:          0
   134217728:          0    268435456:          0    536870912:          0
  1073741824:          0   2147483648:          0
Now its looks much better. Free extents are larger blocks.
Tried extending the filesystem now using fsadm command and its successful now:

# fsadm -F vxfs -b 10485760 /fs_test
UX:vxfs fsadm: INFO: V-3-25942: /dev/vg00/rfstest size increased from 5636096 sectors to 10485760 sectors

# bdf /fs_test 
Filesystem              kbytes    used   avail %used Mounted on
/dev/vg00/fstest      10485760 4097395 5990074   41% /fs_test 

Saturday, October 19, 2013

How To Install and Configure EMC PowerPath License on HPUnix

Question: How do I install EMC Powerpath License?

Answer: Before you start EMC powerpath License installation, please check whether EMCPower Path software is been installed.

1. Checking EMC Powerpath Software installed or not

testhost:/root#swlist -l product EMCpower
# Initializing...
# Contacting target "testhost"...
#
# Target:  testhost:/
#
  EMCpower      HP.5.1.SP2_b113 PowerPath IA64

2. Register EMC Powerpath

Before you can use the EMC powerpath software, you should register it using the EMC Powerpath License key received when you purchased the software from EMC.

Use emcpreg tool to install EMC Powerpath license key as shown below.


# emcpreg -install
===========   EMC PowerPath Registration ===========
Do you have a new registration key or keys to enter?[n] y
Enter the registration keys(s) for your product(s),
one per line, pressing Enter after each key.
After typing all keys, press Enter again.Key (Enter if done): **emc-powerpath-license-key**
1 key(s) successfully added.
Key successfully installed.Key (Enter if done):
Key  is invalid, ignored.
Try again or press Enter if done.
1 key(s) successfully registered.


3. Verify EMC Powerpath Registration

Use EMC powermt command to check the registration as shown below.


# powermt check_registration
Key **emc-powerpath-license-key**
  Product: PowerPath
  Capabilities: All

4. Verify Multiple Paths

Once you’ve installed EMC powerpath, execute powermt display dev=all as shown below to verify whether multiple paths as displayed accordingly.

# powermt display dev=all
Pseudo name=emcpowera
CLARiiON ID=00000000000 [db-server]
Logical device ID=12121212121212 [LUN 1]
state=alive; policy=CLAROpt; priority=0; queued-IOs=0
Owner: default=SP A, current=SP A
==============================================================================
---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---
### HW Path                 I/O Paths    Interf.   Mode    State  Q-IOs Errors
==============================================================================
  1 QLogic Fibre Channel 2300 sdb        SP A4     active  alive      0      0
  1 QLogic Fibre Channel 2300 sdd        SP B4     active  alive      0      0
  2 QLogic Fibre Channel 2300 sdf        SP A5     active  alive      0      0
  2 QLogic Fibre Channel 2300 sdh        SP B5     active  alive      0      0

Monday, September 16, 2013

This target or source is already in use either within this same session or by another session

Error:

# swremove -x mount_all_filesystems=false sudo

=======  09/07/13 04:41:48 METDST  BEGIN swremove SESSION
         (non-interactive) (jobid=testmachine-0125)

       * Session started for user "#".
       
       * Beginning Selection
ERROR:   "testmachine:/":  This target or source is already in use either
         within this same session or by another session.  A read or
         write lock was denied.
       * Target connection failed for "testmachine:/".
ERROR:   More information may be found in the daemon logfile on this
         target (default location is
         testmachine:/var/adm/sw/swagentd.log).
       * Selection had errors.
       
       

=======  09/07/13 04:41:49 METDST  END swremove SESSION
         (non-interactive) (jobid=testmachine-0125)


Solution:
#[/var/adm/sw/products]: ls -lrt|grep swlock
-r--r--r--   1 root       sys              0 Jun 23  2005 swlock


#[/var/adm/sw/products]: mv swlock swlock.bk
#[/var/adm/sw/products]: cd -
/sbin/init.d
#[/sbin/init.d]: /sbin/init.d/swagentd stop
The swagentd daemon is stopped.
#[/sbin/init.d]: /sbin/init.d/swagentd start

Which solved the issue

Friday, August 9, 2013

Starting, Stopping and Aborting Veritas Tasks

When mirrors and RAID5 devices are created with Veritas Volume Manager, the volume contents need to be synchronized to an initial consistent state (e.g., parity and mirrors need to be synchronized). Veritas assigns a unique task id to each operation, and allows tasks to be monitored and displayed with the vxtask(1m) utility:
$ vxtask list
TASKID  PTID TYPE/STATE    PCT   PROGRESS
   172           ATCOPY/R 05.57% 0/209698816/11689984 PLXATT oravol04 oravol04-02 oradg


Since synchronization can be extremely I/O intensive, you might want to pause a synchronization task until a later time. This is easily accomplished by passing the task id to vxtask(1m)’s pause option:

$ vxtask pause 172
$ vxtask list
TASKID  PTID TYPE/STATE    PCT   PROGRESS
   172           ATCOPY/P 05.76% 0/209698816/12077056 PLXATT oravol04 oravol04-02 oradg


Once you are ready to resume the task, you can use vxtask(1m)’s resume option:
$ vxtask resume 172
$ vxtask list
TASKID  PTID TYPE/STATE    PCT   PROGRESS
   172           ATCOPY/R 06.02% 0/209698816/12613632 PLXATT oravol04 oravol04-02 oradg


Similarly, if you want to abort the TaskId you can do it by:

# vxtask abort <taskid>
# vxtask abort 172

This is super useful, and it looks to have caught on.

VxVM vxdisk ERROR V-5-1-2272 NONAMEs2 not a valid dmpnode disk access name.

Storage Team has assigned LUN's, but from one of the enclousre the LUN was visible with the Naming Convention "NONAMEs2"

#  vxdisk -o alldgs list|grep invalid
Disk_3       auto:none       -            -            online invalid
NONAMEs2     auto:none       -            -            online invalid
unix182_157  auto:none       -            -            online invalid
unix182_158  auto:none       -            -            online invalid
unix181_155  auto:none       -            -            online invalid
unix181_156  auto:none       -            -            online invalid
unix181_157  auto:none       -            -            online invalid
unix181_158  auto:none       -            -            online invalid
unix181_159  auto:none       -            -            online invalid
unix181_160  auto:none       -            -            online invalid
unix181_161  auto:none       -            -            online invalid
unix181_162  auto:none       -            -            online invalid
unix181_163  auto:none       -            -            online invalid
unix181_164  auto:none       -            -            online invalid
unix181_165  auto:none       -            -            online invalid

# vxdisk -e list
DEVICE       TYPE      DISK         GROUP        STATUS       OS_NATIVE_NAME   
Disk_0       auto      rootdisk      rootdg       online       c1t0d0s2    
Disk_1       auto      rootmirror    rootdg       online       c1t2d0s2    
Disk_2       auto      spare         rootdg       online       c1t3d0s2    
Disk_3       auto      -             -            online       c1t1d0s2    
VxVM vxdisk ERROR V-5-1-2272 NONAMEs2 not a valid dmpnode disk access name.
NONAMEs2     auto      -             -            online       0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
c1t3d0s2     auto      -             -            error        0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
unix181_0    auto      egndg20d      egndg        online       c2t181d167s2
unix181_1    auto      egndg34d      egndg        online       c2t181d231s2
unix181_2    auto      egndg15b      egndg        online       c2t181d145s2
unix181_3    auto      egndg11b      egndg        online       c2t181d129s2


Soltuion:
To get rid of this, solution is to re-create device mapping, restart vxconfigd, initialize the device, add the disk back to the diskgroup.
# vxdisk rm NONAMEs2 (Remove the device entry in Volume Manager)
# cd /dev/vx/rdmp (Delete all files pertaining to NONAME*)
# cd /dev/vx/dmp (Delete all files pertaining to NONAME*)
# mv /etc/vx/disk.info /etc/vx/disk.info.old
# mv /etc/vx/array.info /etc/vx/array.info.old
# devfsadm -Cv
# vxddladm stop eventsource
# vxconfigd -k (This will recreate the device mapping and the disk.info file)



Remove all the disk with name NONAME
# vxdisk rm NONAMEs2

# pwd
/dev/vx/rdmp
# ls -lrt|grep -i NONAME
crw-------   1 root     other    226,2647 Aug  1 16:55 NONAMEs7
crw-------   1 root     other    226,2646 Aug  1 16:55 NONAMEs6
crw-------   1 root     other    226,2645 Aug  1 16:55 NONAMEs5
crw-------   1 root     other    226,2644 Aug  1 16:55 NONAMEs4
crw-------   1 root     other    226,2643 Aug  1 16:55 NONAMEs3
crw-------   1 root     other    226,2642 Aug  1 16:55 NONAMEs2
crw-------   1 root     other    226,2641 Aug  1 16:55 NONAMEs1
crw-------   1 root     other    226,2640 Aug  1 16:55 NONAMEs0
crw-------   1 root     other    226,2642 Aug  1 16:55 NONAME

# rm NONAME*
# ls -lrt|grep -i NONAME

# cd /dev/vx/dmp  
# ls -lrt|grep -i NONAME
brw-------   1 root     other    226,2647 Aug  1 16:55 NONAMEs7
brw-------   1 root     other    226,2646 Aug  1 16:55 NONAMEs6
brw-------   1 root     other    226,2645 Aug  1 16:55 NONAMEs5
brw-------   1 root     other    226,2644 Aug  1 16:55 NONAMEs4
brw-------   1 root     other    226,2643 Aug  1 16:55 NONAMEs3
brw-------   1 root     other    226,2642 Aug  1 16:55 NONAMEs2
brw-------   1 root     other    226,2641 Aug  1 16:55 NONAMEs1
brw-------   1 root     other    226,2640 Aug  1 16:55 NONAMEs0
brw-------   1 root     other    226,2642 Aug  1 16:55 NONAME
# rm NONAME*
# ls -lrt|grep -i NONAME

# mv /etc/vx/disk.info /etc/vx/disk.info.old
# mv /etc/vx/array.info /etc/vx/array.info.old
# devfsadm -Cv
devfsadm[16972]: verbose: removing file: /devices/pci@9,600000/QLGC,qla@1/st@8,0:
devfsadm[16972]: verbose: removing file: /dev/rmt/0
devfsadm[16972]: verbose: removing file: /devices/pci@9,600000/QLGC,qla@1/st@8,0:n
devfsadm[16972]: verbose: removing file: /dev/rmt/0n
devfsadm[16972]: verbose: removing file: /devices/pci@9,600000/QLGC,qla@1/st@8,0:b
devfsadm[16972]: verbose: removing file: /dev/rmt/0b
devfsadm[16972]: verbose: removing file: /devices/pci@9,600000/QLGC,qla@1/st@8,0:bn
devfsadm[16972]: verbose: removing file: /dev/rmt/0bn
devfsadm[16972]: verbose: removing file: /devices/pci@9,600000/QLGC,qla@1/st@8,0:l
devfsadm[16972]: verbose: removing file: /dev/rmt/0l
devfsadm[16972]: verbose: removing file: /devices/pci@9,600000/QLGC,qla@1/st@8,0:m
devfsadm[16972]: verbose: mknod /devices/pci@9,600000:devctl 0l/3l/20600
The output is much longer, i had shrinked the output.
#


After troubleshooting from vxvm end, Disk are visible now, I will be extending the FS today.

unix182_170  auto      -             -            online       c2t182d248s2
unix182_164  auto      -             -            online       c2t182d249s2
unix182_173  auto      -             -            online       c2t182d250s2
unix182_167  auto      -             -            online       c2t182d251s2
unix182_169  auto      -             -            online       c2t182d252s2
unix182_172  auto      -             -            online       c2t182d253s2
unix182_166  auto      -             -            online       c2t182d254s2
unix182_165  auto      -             -            online       c2t182d255s2
unix182_171  auto      -             -            online       c2t182d173s2
unix182_174  auto      -             -            online       c2t182d175s2
unix182_168  auto      -             -            online       c2t182d177s2

unix181_166  auto      -             -            online       c2t181d248s2
unix181_168  auto      -             -            online       c2t181d249s2
unix181_164  auto      -             -            online       c2t181d250s2
unix181_170  auto      -             -            online       c2t181d251s2
unix181_169  auto      -             -            online       c2t181d252s2
unix181_165  auto      -             -            online       c2t181d253s2
unix181_171  auto      -             -            online       c2t181d254s2
unix181_167  auto      -             -            online       c2t181d255s2
unix181_172  auto      -             -            online       c2t181d173s2
unix181_174  auto      -             -            online       c2t181d181s2
unix181_173  auto      -             -            online       c2t181d199s2

Wednesday, July 24, 2013

lvsplit and lvcreate can return the error: "Argument out of domain".

PROBLEM
lvsplit and lvcreate can return the error: "Argument out of domain".
How to resolve this message?
Example 1: 

# lvsplit /dev/vg01/lvol4
lvsplit: The logical volume "/dev/vg01/lvol4b" could not be created:  
Argument out of domain
lvsplit: Couldn't delete logical volume "/dev/vg01/lvol4b":
The supplied lv number refers to a non-existent logical volume.

Example 2: 
# lvcreate -L 528 -n lvol5 /dev/vg05
lvcreate: the logical volume /dev/vg01/lvol05 could not be created:
Argument out of domain

or

indhost:/dev/dsk # lvcreate -D y -s g -L 361200 -n lvol9 /dev/vg201          
Warning: rounding up logical volume size to extent boundary at size "361216" MB.
lvcreate: The logical volume "/dev/vg201/lvol9" could not be created:
Argument out of domain

RESOLUTION
The formal definition of "Argument out of domain" is "You probably specified an argument a command does not support, or you specified a value to an argument that lies outside the acceptable range. Examine the syntax for the command, make adjustments, and try again."
Both of the example commands above have valid arguments, which indicates the volume group configuration should be checked.
# vgdisplay /dev/vg01
 Max LV   5
 Cur LV   5
indicates that the maximum number of logical volumes has been hit.
max_lv is defined by the -l option when vgcreate was used to create the volume group. From the man page "-l max_lv
Set the maximum number of logical volumes that the volume group is allowed to contain. The default value for max_lv is 255. The maximum number of logical volumes can be a value in the range 1 to 255."
Given this number cannot be changed on-the-fly at 11.x, the volume group will have to be recreated with a higher -l setting.


Tuesday, June 25, 2013

To view installed VxVM license key information

 To view installed VxVM license key information
# vxlicrep

indhost# vxlicrep

Symantec License Manager vxlicrep utility version 3.02.33.0
Copyright (C) 1996-2007 Symantec Corporation. All rights reserved.

Creating a report on all VERITAS products installed on this system

 -----------------***********************-----------------

   License Key                   = R4CE-W6IU-RZ48-WS77-UDDL-SO78-PPPN-V4U
   Product Name                = VERITAS Storage Foundation for Oracle RAC
   Key                               = Invalid, Key EXPIRED -936 days ago

   License Type                  = DEMO
   OEM ID                          = 4095
   Demo End Date              = Tue Apr 15 01:00:00 2008
                                       (expired -936.8 days ago).
   Editions Product             = YES

To Remove the VxVM Installed License Key

The license keys reported by /opt/VRTS/bin/vxlicrep are stored in the /etc/vx/licenses/lic directory with a .vxlic extension. For example, vxlicrep reports:

-----------------***********************-----------------
License Key = I4CU-WLID-P6BN-BAWG-OSF7-CC29-7LGC-P
Product Name = VERITAS Storage Foundation for Cluster File System
Key = Invalid, Key EXPIRED -1 days ago
License Type = DEMO
OEM ID = 4095
Demo End Date = Thu Mar 29 01:00:00 2007
(expired -1.4 days ago).
Editions Product = YES

#pwd
/etc/vx/licenses/lic
#ls -l


-rw-r--r-- 1 root root 32 Jan 29 07:12 I4CU-WLID-P6BN-BFWG-OSF7-CC29-7LGC-P.vxlic

To remove the license key I4CU-WLID-P6BN-BAWG-OSF7-CC29-7LGC-P for the VERITAS Storage Foundation for Cluster File System product,

#rm I4CU-WLID-P6BN-BFWG-OSF7-CC29-7LGC-P.vxlic
Rerun /opt/VRTS/bin/vxlicrep. The license will no longer be displayed

Verifying VxVM Package Installation

To verify packages installation, use OS-specific commands:
•    Solaris
o    pkginfo –l VRTSvxvm

•    HP-UX
o    swlist –l product VRTSvxvm

•    AIX
o    lslpp –l VRTSvxvm

•    Linux
o    rpm –qi VRTSvxvm

VxVm Command Log File

•    Located in /var/adm/vx/veacmdlog
•    Display a history of tasks performed in the current session and in previous sessions.
•    Example of Command log file entry:

Description: Create Volume
Date: November 24, 2009  3:59:45 PM PST
Command: /usr/sbin/vxassist   -g cdcxpd0030dg -b make lv02 27262976s layout=nostripe comment='lv02 local application volume'
Output: VxVM vxassist WARNING V-5-1-370 -b (background) operation incompatible with active-type initialization, ignored
Exit Code: 0

How to check whether the given depot will require reboot or not for installation

We can check whether following software will take reboot or not:

indhost:/var/adm/crash# swlist -l fileset -s /var/adm/crash/scsiU320-00_B.11.23.0809_HP-UX_B.11.23_IA_PA.depot -a is_reboot
# Initializing...
# Contacting target "indhost"...
#
# Target:  indhost:/var/adm/crash/scsiU320-00_B.11.23.0809_HP-UX_B.11.23_IA_PA.depot
#

# scsiU320                     
  scsiU320.SCSIU320-KRN         true      This Fileset will take Reboot        
  scsiU320.SCSIU320-KRN         true      This Fileset will take Reboot          
  scsiU320.SCSIU320-RUN         false     This Fileset will not required reboot  
  scsiU320.SCSIU320-RUN         false     This Fileset will not required reboot 

So For installing package scsiU320-00_B.11.23.0809_HP-UX_B.11.23_IA_PA.depot we require an reboot of the host.  

Monday, June 24, 2013

To Display a summary for all disk in VxVM

# vxdisk –s list
ranhost# vxdisk -s list
Disk:   IBM_VSCSI0_1
type:   auto
flags:  LVM online error private autoconfig
error:  Disk is not useable, bad format
guid:   -
udid:   AIX%5FVDASD%5FVSCSI%5F240C50%2002D0B349A06OPEN-V07HITACH
info:   format=LVM

Disk:   TagmaStore-USP0_1
type:   auto
flags:  online ready private autoconfig autoimport imported
guid:   {6bac2e3a-1dd2-11b2-ad3c-07d26e3363fa}
udid:   HITACHI%5FOPEN-V%5F0F3E5%5F30A6
site:    -
diskid: 1207570576.22.indhost
dgname: testdg
dgid:   1207570654.24.indhost
hostid: indhost
info:   format=cdsdisk,privoffset=256

Disk:   TagmaStore-USP1_0
type:   auto
flags:  online ready private autoconfig autoimport imported
guid:   {f09972f6-1dd1-11b2-a9c6-411625324c5f}
udid:   HITACHI%5FOPEN-V%5F0F3F1%5F2070
site:    -
diskid: 1207570799.27.indhost
dgname: rootdg
dgid:   1207572000.35.indhost
hostid: indhost
info:   format=cdsdisk,privoffset=256

For One particular disk

# vxdisk -s list c2t0d0

Disk:   c2t0d0
type:   auto
flags:  online ready private autoconfig invalid
guid:   -
udid:   HP%2073.4G%5FST373454LC%5FDISKS%5F3KP2YXHV%20%20%20%20
site:    -
diskid:
dgname:
dgid:  
hostid:
info:   format=none

Reserving disks in VxVm

70.1    Setting Reservation On
By default, the vxassist command allocates space from any disk that has free space. You can reserve a set of disks for special purposes, such as to avoid general use of a particularly slow or a particularly fast disk.
To reserve a disk for special purposes, use the following command:

# vxedit -g testdg set reserve=on disk01

indhost# vxdisksetup -i TagmaStore-USP0_1
indhost# vxdisksetup -i TagmaStore-USP1_0
indhost# vxdg init testdg disk01=TagmaStore-USP0_1
indhost# vxdg -g testdg adddisk disk02=TagmaStore-USP1_0
indhost# vxedit -g testdg set reserve=on disk01
indhost# vxassist -g testdg make testvol 500M
indhost# vxprint -ht testvol
Disk group: testdg

V  NAME         RVG/VSET/CO  KSTATE   STATE    LENGTH   READPOL   PREFPLEX UTYPE
PL NAME         VOLUME       KSTATE   STATE    LENGTH   LAYOUT    NCOL/WID MODE
SD NAME         PLEX         DISK     DISKOFFS LENGTH   [COL/]OFF DEVICE   MODE
SV NAME         PLEX         VOLNAME  NVOLLAYR LENGTH   [COL/]OFF AM/NM    MODE
SC NAME         PLEX         CACHE    DISKOFFS LENGTH   [COL/]OFF DEVICE   MODE
DC NAME         PARENTVOL    LOGVOL
SP NAME         SNAPVOL      DCO
EX NAME         ASSOC        VC                       PERMS    MODE     STATE
SR NAME         KSTATE

v  testvol      -            ENABLED  ACTIVE   1024000  SELECT    -        fsgen
pl testvol-01   testvol      ENABLED  ACTIVE   1024000  CONCAT    -        RW
sd disk02-01    testvol-01   disk02   0        1024000  0         TagmaStore-USP1_0 ENA


After you enter this command, the vxassist program does not allocate space from the selected disk (disk01) unless that disk is specifically mentioned on the vxassist command line. For example, if disk01 is reserved, use the following command:

indhost# vxassist -g testdg make testvol 500M disk01
indhost# vxprint -th testvol
Disk group: testdg

V  NAME         RVG/VSET/CO  KSTATE   STATE    LENGTH   READPOL   PREFPLEX UTYPE
PL NAME         VOLUME       KSTATE   STATE    LENGTH   LAYOUT    NCOL/WID MODE
SD NAME         PLEX         DISK     DISKOFFS LENGTH   [COL/]OFF DEVICE   MODE
SV NAME         PLEX         VOLNAME  NVOLLAYR LENGTH   [COL/]OFF AM/NM    MODE
SC NAME         PLEX         CACHE    DISKOFFS LENGTH   [COL/]OFF DEVICE   MODE
DC NAME         PARENTVOL    LOGVOL
SP NAME         SNAPVOL      DCO
EX NAME         ASSOC        VC                       PERMS    MODE     STATE
SR NAME         KSTATE

v  testvol      -            ENABLED  ACTIVE   1024000  SELECT    -        fsgen
pl testvol-01   testvol      ENABLED  ACTIVE   1024000  CONCAT    -        RW
sd disk01-02    testvol-01   disk01   1024000  1024000  0         TagmaStore-USP0_1 ENA


The vxassist command overrides the reservation and creates a 500 megabyte volume on testdg.

70.2    To turn off reservation of a disk

indhost# vxedit -g testdg set reserve=off disk01
indhost# vxassist -g testdg remove volume testvol
indhost# vxassist -g testdg make testvol 500M
indhost# vxprint -ht testvol
Disk group: testdg

V  NAME         RVG/VSET/CO  KSTATE   STATE    LENGTH   READPOL   PREFPLEX UTYPE
PL NAME         VOLUME       KSTATE   STATE    LENGTH   LAYOUT    NCOL/WID MODE
SD NAME         PLEX         DISK     DISKOFFS LENGTH   [COL/]OFF DEVICE   MODE
SV NAME         PLEX         VOLNAME  NVOLLAYR LENGTH   [COL/]OFF AM/NM    MODE
SC NAME         PLEX         CACHE    DISKOFFS LENGTH   [COL/]OFF DEVICE   MODE
DC NAME         PARENTVOL    LOGVOL
SP NAME         SNAPVOL      DCO
EX NAME         ASSOC        VC                       PERMS    MODE     STATE
SR NAME         KSTATE

v  testvol      -            ENABLED  ACTIVE   1024000  SELECT    -        fsgen
pl testvol-01   testvol      ENABLED  ACTIVE   1024000  CONCAT    -        RW
sd disk02-01    testvol-01   disk02   0        1024000  0         TagmaStore-USP1_0 ENA

Initialize a data or non-boot disk

# /etc/vx/bin/vxdisksetup -i c2t0d2
VxVM vxdisk ERROR V-5-1-3421 Device c2t0d2 is already in use by LVM.
# pvremove /dev/rdsk/c2t0d2
The physical volume associated with "/dev/rdsk/c2t0d2" has been removed.
 
# /etc/vx/bin/vxdisksetup -i c2t0d2
 
# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
c0t0d0s2     auto            -            -            LVM
c2t0d2       auto:cdsdisk    -            -            online

indhost# /etc/vx/bin/vxdisksetup -if TagmaStore-USP0_1
indhost# /etc/vx/bin/vxdisksetup -if TagmaStore-USP1_0
indhost# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
IBM_VSCSI0_1 auto:LVM        -            -            LVM
TagmaStore-USP0_1 auto:cdsdisk    -            -            online
TagmaStore-USP1_0 auto:cdsdisk    -            -            online

Getting an LDEV of LUNs in AIX

indhost# vxdisk list GENESIS1_163
Device:    GENESIS1_163
devicetag: GENESIS1_163
type:      auto
info:      format=none
flags:     online ready private autoconfig invalid
pubpaths:  block=/dev/vx/dmp/GENESIS1_163 char=/dev/vx/rdmp/GENESIS1_163
guid:      -
udid:      HITACHI%5FOPEN-V%5F0F3E5%5F20E3
site:      -
Multipathing information:
numpaths:   2
hdisk427        state=enabled
hdisk0  state=enabled

indhost# lsattr -El hdisk427
PR_key_value   none               Reserve Key                      True
clr_q          no                 Device CLEARS its Queue on error True
location                          Location Label                   True
lun_id         0xa2000000000000   Logical Unit Number ID           False
max_transfer   0x40000            Maximum TRANSFER Size            True
node_name      0x50060e8004f3e532 FC Node Name                     False
pvid           none               Physical Volume ID               False
q_err          yes                Use QERR bit                     False
q_type         simple             Queue TYPE                       True
queue_depth    2                  Queue DEPTH                      True
reassign_to    120                REASSIGN time out                True
reserve_policy single_path        Reserve Policy                   True
rw_timeout     60                 READ/WRITE time out              True
scsi_id        0xd12900           SCSI ID                          False
start_timeout  60                 START UNIT time out              True
ww_name        0x50060e8004f3e532 FC World Wide Name               False

Rename a disk in a diskgroup

Throough VEA:
  • Select the disk that you want to rename.
  • Select Actions-> Rename Disk.
  • Specify the original disk name and the new name
Through Command Line:

vxedit rename:

Syntax: # vxedit –g <dg_name> rename <old_disk_name> <new_disk_name>
 
Example

Before:-
indhost# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
IBM_VSCSI0_1 auto:LVM        -            -            LVM
TagmaStore-USP0_1 auto:cdsdisk    disk01       markdg       online
TagmaStore-USP1_0 auto:cdsdisk    disk02       markdg       online
indhost# vxedit -g markdg rename disk02 disk03

After:-
indhost# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
IBM_VSCSI0_1 auto:LVM        -            -            LVM
TagmaStore-USP0_1 auto:cdsdisk    disk01       markdg       online
TagmaStore-USP1_0 auto:cdsdisk    disk03       markdg       online

Making a Bootable LVM Copy of a VxVM Boot Disk

•    System should be at run level 1
•    Use the command /etc/vx/bin/vxres_lvmroot
o    –b sets primary and/or alternate boot paths
o    –v verbose
•    Example:
# /etc/vx/bin/vxres_lvmroot –v –b c3t5d0
o    creates a LVM copy of the current VxVM boot disk to c3t5d0
o    sets the primary boot path to c3t5d0

# bdf
Filesystem          kbytes    used   avail %used Mounted on
/dev/vx/dsk/rootdg/rootvol
                   1048576  415148  593863   41% /
/dev/vx/dsk/rootdg/standvol
                   2064384  325568 1630227   17% /stand
/dev/vx/dsk/rootdg/varvol
                   8388608  702724 7205630    9% /var
/dev/vx/dsk/rootdg/usrvol
                   8388608 2667083 5364031   33% /usr
/dev/vx/dsk/rootdg/tmpvol
                    524288   17378  475360    4% /tmp
/dev/vx/dsk/rootdg/optvol
                   8388608 4377947 3760007   54% /opt
/dev/vx/dsk/rootdg/homevol
                    131072    1662  121326    1% /home
DevFS                    3       3       0  100% /dev/deviceFileSystem

# setboot
Primary bootpath : 0/1/1/1.0x2.0x0 (/dev/rdisk/disk71)
HA Alternate bootpath :
Alternate bootpath : 0/1/1/0.0x0.0x0 (/dev/rdisk/disk70)

Autoboot is ON (enabled)

# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
c2t0d0s2     auto:hpdisk     rootdisk02   rootdg       online
c2t1d0s2     auto:LVM        -            -            LVM
c3t2d0s2     auto:hpdisk     rootdisk01   rootdg       online
c5t0d1       auto:cdsdisk    rootdg02     rootdg       online
c5t0d2       auto:cdsdisk    rootdg03     rootdg       online
c5t0d3       auto:cdsdisk    rootdg04     rootdg       online
c5t0d4       auto:cdsdisk    rootdg05     rootdg       online
c5t0d5       auto:cdsdisk    rootdg06     rootdg       online
c5t0d6       auto:cdsdisk    rootdg07     rootdg       online
c5t0d7       auto:cdsdisk    rootdg08     rootdg       online
c5t1d0       auto:cdsdisk    rootdg01     rootdg       online

# /etc/vx/bin/vxres_lvmroot -v -b c2t1d0s2
vxres_lvmroot 14:37: Gathering information on the current VxVM root config
vxres_lvmroot 14:38: Checking specified disk(s) for usability
vxres_lvmroot 14:38: Preparing disk c2t1d0s2 as an LVM root disk
vxres_lvmroot 14:38: Creating LVM Volume Group vg00
vxres_lvmroot 14:38: Copying /dev/vx/dsk/rootdg/standvol (hfs) to /dev/vg00/lvol1
vxres_lvmroot 14:38: Cloning /dev/vx/dsk/rootdg/swapvol (swap) to /dev/vg00/lvol2
vxres_lvmroot 14:38: Copying /dev/vx/dsk/rootdg/rootvol (vxfs) to /dev/vg00/lvol3
vxres_lvmroot 14:39: Copying /dev/vx/dsk/rootdg/homevol (vxfs) to /dev/vg00/lvol4
vxres_lvmroot 14:39: Copying /dev/vx/dsk/rootdg/tmpvol (vxfs) to /dev/vg00/lvol5
vxres_lvmroot 14:39: Copying /dev/vx/dsk/rootdg/usrvol (vxfs) to /dev/vg00/lvol6
vxres_lvmroot 15:00: Copying /dev/vx/dsk/rootdg/optvol (vxfs) to /dev/vg00/lvol7
vxres_lvmroot 15:16: Copying /dev/vx/dsk/rootdg/varvol (vxfs) to /dev/vg00/lvol8
vxres_lvmroot 15:20: Setting up disk c2t6d0 as an LVM boot disk
vxres_lvmroot 15:21: Installing fstab and fixing dev nodes on ne
root FS
vxres_lvmroot 15:21: Current setboot values:
vxres_lvmroot 15:21: Primary: 0/0/2/0.6.0
vxres_lvmroot 15:21: Alternate: 0/4/0/0.12.0
vxres_lvmroot 15:21: Making disk c2t6d0 (0/0/2/1.6.0) the primary boot disk
vxres_lvmroot 15:21: Making disk c1t6d0 (0/0/2/0.6.0) the alternate boot disk


vxres_lvmroot 15:21: Disk c2t6d0 is now an LVM (VG vg00) rootable boot disk

# setboot
Primary bootpath : 0/1/1/0.0x1.0x0 (/dev/rdisk/disk69)
HA Alternate bootpath :
Alternate bootpath : 0/1/1/1.0x2.0x0 (/dev/rdisk/disk71)

Making a Bootable VxVM Copy of an LVM Boot Disk

•    System should be at run level 1
•    swagentd has to be running
•    Use the command /etc/vx/bin/vxcp_lvmroot
o    Initializes a specified physical disk as a VxVM root disk named rotodisk## (where ## is the first number starting at 01 that creates a unique disk name)
o    Copies the contents of the volumes on the LVM root disk to the new VxVM root disk.
o    Optionally creates a mirror of the VxVM root disk on another specified physical disk.
•    Options for vxcp_lvmroot
o    –b sets primary and/or alternate boot paths
o    –v verbose
o    –R reduce file system sizes by percent
o    –m creates a root mirror of the VxVM copy
•    Example using all of the options”
# /etc/vx/bin/vxcp_lvmroot –m c4t6d0 –R 20 –v –b c3t5d0
o    creates a VxVM copy of the current LVM boot disk to c3t5d0
o    reduce each volume/filesystem size on the copy by 20%
o    sets the primary boot path to c3t5d0
o    makes a mirrored VxVM boot disk on c4t6d0
o    sets the alternate boot path to c4t6d0

The above recommendation to run vxcp_lvmroot at run level 1 does not work without starting a few services.

# /sbin/init.d/net.init start
#/sbin/init.d/net start
#/sbin/init.d/swagentd start
#/etc/vx/bin/vxcp_lvmroot –m c4t6d0 –R 20 –v –b c3t5d0


The following exampled shows how to setup up a VxVM root disk on physical disk c3t2d0

# bdf
Filesystem          kbytes    used   avail %used Mounted on
/dev/vx/dsk/rootdg/rootvol
                   1048576  414917  594082   41% /
/dev/vx/dsk/rootdg/standvol
                   2064384  325562 1630233   17% /stand
/dev/vx/dsk/rootdg/varvol
                   8388608  702152 7206179    9% /var
/dev/vx/dsk/rootdg/usrvol
                   8388608 2667083 5364031   33% /usr
/dev/vx/dsk/rootdg/tmpvol
                    524288   17379  475359    4% /tmp
/dev/vx/dsk/rootdg/optvol
                   8388608 4377947 3760007   54% /opt
/dev/vx/dsk/rootdg/homevol
                    131072    1662  121326    1% /home
DevFS                    3       3       0  100% /dev/deviceFileSystem

# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
c2t0d0s2     auto:hpdisk     -            -            online
c2t1d0s2     auto:LVM        -            -            LVM
c3t2d0s2     auto:hpdisk     rootdisk01   rootdg       online
c5t0d1       auto:cdsdisk    rootdg02     rootdg       online
c5t0d2       auto:cdsdisk    rootdg03     rootdg       online
c5t0d3       auto:cdsdisk    rootdg04     rootdg       online
c5t0d4       auto:cdsdisk    rootdg05     rootdg       online
c5t0d5       auto:cdsdisk    rootdg06     rootdg       online
c5t0d6       auto:cdsdisk    rootdg07     rootdg       online
c5t0d7       auto:cdsdisk    rootdg08     rootdg       online
c5t1d0       auto:cdsdisk    rootdg01     rootdg       online

# /etc/vx/bin/vxcp_lvmroot -v -b c3t2d0
VxVM vxcp_lvmroot INFO V-5-2-4668 01:13: Bootdisk is configured with new-style DSF
VxVM vxcp_lvmroot INFO V-5-2-2499 01:13: Gathering information on LVM root volume group vg00
VxVM vxcp_lvmroot INFO V-5-2-2441 01:13: Checking specified disk(s) for usability
VxVM vxcp_lvmroot INFO V-5-2-4679 01:13: Using legacy-style DSF names
VxVM vxcp_lvmroot INFO V-5-2-2566 01:13: Preparing disk c3t2d0 as a VxVM root disk
VxVM vxcp_lvmroot INFO V-5-2-3767 01:13: Disk c3t2d0 is now EFI partitioned disk c3t2d0s2
VxVM vxcp_lvmroot INFO V-5-2-2537 01:13: Initializing DG rootdg with disk c3t2d0s2 as DM rootdisk01
VxVM vxcp_lvmroot INFO V-5-2-1606 01:13: Copying /dev/vg00/lvol1 (vxfs) to
/dev/vx/dsk/rootdg/standvol
VxVM vxcp_lvmroot INFO V-5-2-1604 01:13: Cloning /dev/vg00/lvol2 (swap) to
/dev/vx/dsk/rootdg/swapvol
VxVM vxcp_lvmroot INFO V-5-2-1606 01:13: Copying /dev/vg00/lvol3 (vxfs) to
/dev/vx/dsk/rootdg/rootvol
VxVM vxcp_lvmroot INFO V-5-2-1606 01:14: Copying /dev/vg00/lvol4 (vxfs) to
/dev/vx/dsk/rootdg/tmpvol
VxVM vxcp_lvmroot INFO V-5-2-1606 01:14: Copying /dev/vg00/lvol5 (vxfs) to
/dev/vx/dsk/rootdg/homevol
VxVM vxcp_lvmroot INFO V-5-2-1606 01:14: Copying /dev/vg00/lvol6 (vxfs) to
/dev/vx/dsk/rootdg/optvol
VxVM vxcp_lvmroot INFO V-5-2-1606 01:21: Copying /dev/vg00/lvol7 (vxfs) to
/dev/vx/dsk/rootdg/usrvol
VxVM vxcp_lvmroot INFO V-5-2-1606 01:24: Copying /dev/vg00/lvol8 (vxfs) to
/dev/vx/dsk/rootdg/varvol
VxVM vxcp_lvmroot INFO V-5-2-4678 01:25: Setting up disk c3t2d0s2 as a boot disk
VxVM vxcp_lvmroot INFO V-5-2-1638 01:25: Installing fstab and fixing dev nodes on new root
FS
rm: /tmpmnt.13911.30026//etc/vx/darecs non-existent
VxVM vxcp_lvmroot INFO V-5-2-2538 01:26: Installing bootconf & rootconf files in new stand
FS
VxVM vxcp_lvmroot INFO V-5-2-2462 01:26: Current setboot values:
VxVM vxcp_lvmroot INFO V-5-2-2569 01:26: Primary: 0/1/1/0.0x1.0x0 /dev/rdisk/disk70
VxVM vxcp_lvmroot INFO V-5-2-2416 01:26: Alternate:
VxVM vxcp_lvmroot INFO V-5-2-4676 01:26: Making disk /dev/rdisk/disk71_p2 the primary boot
disk
VxVM vxcp_lvmroot INFO V-5-2-4663 01:26: Making disk /dev/rdisk/disk70_p2 the alternate
boot disk
VxVM vxcp_lvmroot INFO V-5-2-4671 01:26: Disk c3t2d0s2 is now a VxVM rootable boot disk

Note: The –b option to vxcp_lvmroot uses the setboot command to define c3t2d0 as the primary boot device. If this option is not specified, the primary boot device is not changed.

If the destination VxVM root disk is not big enough to accommodate the contents of the LVM root disk, you can use the –R option to specify a percentage by which to reduce the size of the file systems on the target disk. (This takes advantage of the fact that most of these file systems are usually nowhere near 100% full.) For example, to specify a size reduction of 30%, the following command would be used:

# /etc/vx/bin/vxcp_lvmroot –R 30 -v -b c3t2d0s2

The next example uses the same command and additionally specifies the –m options to set up a root mirror on disk c2t0d0s2

# /etc/vx/bin/vxcp_lvmroot –m c2t0d0s2 –R 30 -v -b c3t2d0s2

In this example, the –b options to vxcp_lvmroot sets c3t2d0 as the primary boot device and c2t0d0 as the alternate boot device. This command is equivalent to using vxcp_lvmroot to create the VxVM-rootable disk, and then using the vxrootmir to create the mirror:

# /etc/vx/bin/vxcp_lvmroot -v -b c3t2d0s2
# /etc/vx/bin/vxrootmir –v –b c2t0d0s2

# /etc/vx/bin/vxrootmir -v -b c2t0d0s2
VxVM vxrootmir INFO V-5-2-2501 03:26: Gathering information on the current VxVMn
VxVM vxrootmir INFO V-5-2-2441 03:26: Checking specified disk(s) for usability
VxVM vxrootmir INFO V-5-2-4679 03:26: Using legacy-style DSF names
VxVM vxrootmir INFO V-5-2-2566 03:26: Preparing disk disk70_p2 as a VxVM root dk
VxVM vxrootmir INFO V-5-2-3766 03:26: Disk disk70_p2 is now EFI partitioned dis2
VxVM vxrootmir INFO V-5-2-2410 03:26: Adding disk disk70_p2 to rootdg as DM roo2
VxVM vxrootmir INFO V-5-2-1646 03:26: Mirroring all volumes on root disk
VxVM vxrootmir INFO V-5-2-1648 03:26: Mirroring volume standvol
VxVM vxrootmir INFO V-5-2-1648 03:27: Mirroring volume swapvol
VxVM vxrootmir INFO V-5-2-1648 03:31: Mirroring volume rootvol
VxVM vxrootmir INFO V-5-2-1648 03:31: Mirroring volume tmpvol
VxVM vxrootmir INFO V-5-2-1648 03:32: Mirroring volume homevol
VxVM vxrootmir INFO V-5-2-1648 03:32: Mirroring volume optvol
VxVM vxrootmir INFO V-5-2-1648 03:36: Mirroring volume usrvol
VxVM vxrootmir INFO V-5-2-1648 03:39: Mirroring volume varvol
VxVM vxrootmir INFO V-5-2-2462 03:43: Current setboot values:
VxVM vxrootmir INFO V-5-2-2569 03:43: Primary:  0/1/1/1.0x2.0x0 /dev/rdisk/disk1
VxVM vxrootmir INFO V-5-2-2416 03:43: Alternate:        0/1/1/0.0x1.0x0 /dev/rd9
VxVM vxrootmir INFO V-5-2-2551 03:43: Making mirror disk disk70 (/dev/rdisk/disk
Alternate boot path set to 0/1/1/0.0x0.0x0 (/dev/rdisk/disk70)
VxVM vxrootmir INFO V-5-2-1616 03:43: Disk c2t0d0 is now a mirrored root disk


The disk name assigned to the VxVM root disk mirror also uses the format rootdisk## with ## set to the next available number.

Before:
# setboot
Primary bootpath : 0/1/1/1.0x2.0x0 (/dev/rdisk/disk71)
HA Alternate bootpath :
Alternate bootpath : 0/1/1/0.0x1.0x0 (/dev/rdisk/disk69)

After:
# setboot
Primary bootpath : 0/1/1/1.0x2.0x0 (/dev/rdisk/disk71)
HA Alternate bootpath :
Alternate bootpath : 0/1/1/0.0x0.0x0 (/dev/rdisk/disk70)

# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
c2t0d0s2     auto:hpdisk     rootdisk02   rootdg       online
c2t1d0s2     auto:LVM        -            -            LVM
c3t2d0s2     auto:hpdisk     rootdisk01   rootdg       online
c5t0d1       auto:cdsdisk    rootdg02     rootdg       online
c5t0d2       auto:cdsdisk    rootdg03     rootdg       online
c5t0d3       auto:cdsdisk    rootdg04     rootdg       online
c5t0d4       auto:cdsdisk    rootdg05     rootdg       online
c5t0d5       auto:cdsdisk    rootdg06     rootdg       online
c5t0d6       auto:cdsdisk    rootdg07     rootdg       online
c5t0d7       auto:cdsdisk    rootdg08     rootdg       online
c5t1d0       auto:cdsdisk    rootdg01     rootdg       online

# vxdg free
GROUP        DISK         DEVICE       TAG          OFFSET    LENGTH    FLAGS
rootdg       rootdg01     c5t1d0       c5t1d0       0         4145024   -
rootdg       rootdg02     c5t0d1       c5t0d1       0         9387904   -
rootdg       rootdg03     c5t0d2       c5t0d2       0         4145024   -
rootdg       rootdg04     c5t0d3       c5t0d3       0         4145024   -
rootdg       rootdg05     c5t0d4       c5t0d4       0         4145024   -
rootdg       rootdg06     c5t0d5       c5t0d5       0         4145024   -
rootdg       rootdg07     c5t0d6       c5t0d6       0         4145024   -
rootdg       rootdg08     c5t0d7       c5t0d7       0         4145024   -
rootdg       rootdisk01   c3t2d0s2     c3t2d0s2     37322752  33440672  -
rootdg       rootdisk02   c2t0d0s2     c2t0d0s2     37322752  33440672  -