Unix Addiction

1.-Check server master what is the master server #vxdctl -c mode mode: enabled: cluster active - SLAVE master: linuxtest1 2.-Master Server ------------------ ------------------ linuxtest1 2.1.-Slave Server ------------------ ------------------ linuxtest2 3.-Connect to master server --------------------------- --------------------------- ssh linuxtest1 4.-Check DG and FS before the change in our case we will increase data03  #vxassist -g POE-dg  maxgrow data03 #vxassist -g POE-dg  maxsize data03 5.-Check Disks availables for adding in the Disk Group we discover the new disk sdat/sdau/sdav, that are in online status, however they are not part from any DG #vxdisk -o alldgs list DEVICE       TYPE            DISK         GROUP        STATUS cciss/c0d0   auto:none       -            -            online invalid sda          auto:cdsdisk    POE-54  POE-dg  online shared sdaa         auto:cdsdisk    -            -            online sdab         au

BTRF FILE SYSTEM ON RED HAT 1.-CREATING A BTRF FILE SYSTEM M mkfs.btrfs / dev / device   # mkfs.btrfs / dev / sdc1     2.-MOUNTING A BTRF FILE SYSTEM   mount / dev / device / mount-point   # mount / dev / sdc1 / btrfstest   3.-RESIZING A BTRF FILE SYSTEM    You can increase the btrs file system in this case +200M   btrfs filesystem resize amount / mount-point   #btrfs filesystem resize +500M /btrfstst   Resize '/btrfstest' of '+500M'    4.-SHRINKING A BTRFS FILE SYSTEM btrfs filesystem show / mount-point + devid 1 size 1.00GiB used 224.75MiB path /dev/vda devid 2 size 400.00MiB used 204.75MiB path /dev/vdb devid 3 size 2.00GiB used 8.00MiB path /dev/vdc devid 4 size 3.00GiB used 8.00MiB path /dev/vdd btrfs filesystem resize devid : amount /mount-point   # btrfs filesystem resize 2:300M /btrfstest  Resize '/btrfstest' of '2:300M'  You has reduced the file system to 300M, you wi

Creating the metaset is a simple process. First of all we define our metaset and add our host to it. bash-3.00# metaset -s test -a -h avalon Syntax is pretty straightforward: -s is used to specify which metaset we’re using -a is the add flag. Guess what -d does? -h specifies the hostname which owns this metaset All metasets are owned by at least one host (it’s how they track who can access them). If you’re in a cluster environment, multiple hosts will own the metaset, allowing the cluster software to move the metadevices between nodes. For a single hosted metaset, however, we just need to add one host, and we need to make sure that it will automatically take ownership and import the metaset on boot. All we have to do to make this happen is enable the autotake flag on the metaset: bash-3.00# metaset -s test -A enable And that completes the setup of the metaset. We then just select which LUNs we’re interested in, and add them in to the metaset: bash-3.00# metaset -s test -a

1.-Create   Metaset Called "oracle_set" to the host lab01 , This Step Can Be Not Executed If The Metaset Is Created #metaset -s oracle_set -a -h lab01 -a Adds drives or hosts to the named set. -h   Specifies one or more host names to be added to or deleted from a diskset. 2.-If you have the LUN’s allocated in the server you can add each one to the configuration, in this case we have 5 disk to aggregate to the diskset   2.1Just in case in order to discover “devfsadm” or cfgadm –c configure cX CX=Controller Number #metaset -s oracle_set -a c2txxxxxxxxxxxxxxxxd0 #metaset -s oracle_set -a c2txxxxxxxxxxxxxxxxd0 #metaset -s oracle_set -a c2xxxxxxxxxxxxxxxxxd0 #metaset -s oracle_set -a c2xxxxxxxxxxxxxxxxxd0 #metaset -s oracle_set -a c2xxxxxxxxxxxxxxxxxd0 3-After adding the LUN’s to the diskset created, you can check them with the command below #metaset 3-You can check with prtvtoc the partition for each disk and change it if you

1.-How to clean failing in a disk or group disks # vxdisk list | grep fail  c1t0d0s2 auto:sliced rootdisk rootdg online failing  c1t1d0s2 auto:sliced disk01    rootdg   online failing The command is the following # vxedit -g <DISK_GROUP NAME> set failing=off <DISK_NAME> # vxedit -g rootdg set failing=off rootdisk # vxedit -g rootdg set failing=off disk01 Verify the disk in order to check if the "FAILING" was cleaned # vxdisk list | grep fail c1t0d0s2 auto:sliced rootdisk rootdg online c1t1d0s2 auto:sliced disk01 rootdg online  

How to recover and start a Veritas Volume Manager logical volume where the volume is DISABLED ACTIVE and has a plex that is DISABLED RECOVER Article : TECH8501 | Created : 2007-01-08 | Updated : 2011-04-06 | Article URL http://www.symantec.com/docs/ TECH8501 How to recover and start a Veritas Volume Manager logical volume where the volume is DISABLED ACTIVE and has a plex that is DISABLED RECOVER Solution When a system encounters a problem with a volume or a plex, or if Veritas Volume Manager (VxVM) has any reason to believe that the data is not synchronized, VxVM changes the kernel state, KSTATE and state, STATE, of the volume and its plexes accordingly. The plex state can be stale, empty, nodevice, etc. A particular plex state does not necessarily mean that the data is good or bad. The plex state is representative of VxVM's perception of the data in a plex. The output from the vxprint utility using the switches "-h" and

1.-How to check the HW and Transport Errors root@ # iostat -en   ---- errors ---   s/w h/w trn tot device     0   0   0   0 md/d20     0   0   0   0 md/d21     0   0   0   0 md/d25     0   0   0   0 md/d26     0   0   0   0 md/d60     0   0   0   0 md/d61     0   0   0   0 md/d65     0   0   0   0 md/d66     0   0   0   0 md/d80     0   0   0   0 md/d81     0   0   0   0 md/d85     0   0   0   0 md/d86     0   6   6   12 c0t1d0     0   0   0   0 c0t0d0     0   0   0   0 c0t3d0     0   0   0   0 c5t0d0     0   0   0   0 c5t1d0 3.-Verify the metadevices in maintenance #metastat d20: Mirror     Submirror 0: d60       State: Okay     Submirror 1: d80       State: Okay     Pass: 1     Read option: roundrobin (default)     Write option: parallel (default)     Size: 104862500 blocks (50 GB)d1: Submirror of d0     State: Needs maintenance     Invoke: metareplace d20 c1t0d0s0 <new device>     Size: 16780224 blocks (8.0 GB)     Stripe 0:         Device     Start Block  Dbase        State R

You can detect what disk is with issues on the server #vxprint -htr | more dg rootdg       default      default  70000    1165523746.8. dm disk01       -            -        -        -                  NODEVICE        <--- Disk Broken dm rootdisk     c1t0d0s2     auto     20351    143328960 - Just in case you can check to the devalias assigned to the disk failed #eeprom |grep devalias devalias vx-disk01 /pci@1f,700000/scsi@2/disk@1,0:a devalias vx-rootdisk /pci@1f,700000/scsi@2/disk@0 , You can run a cfgadm in order to check if the disk is available # cfgadm -avl unavailable  unavailable  n   /devices/pci@1f,700000/scsi@2:scsi::dsk/c1t1d0      <---Disk With Issues c1::dsk/c1t2d0                 connected    configured   unknown    HITACHI  HUS10733ASUN72G We will proceed now to offline the disk a perform the remove to replace the disk (disk01) #vxdisk offline disk01 #vxdisk rm disk01 Checking the disk status #vxprint -htr | more Disk group: rootdg dg rootdg       default      def