• Learning Map
  • Unix Quiz Center
  • Unix Professional Network
  • Just-Unix-No-Noise FB Group

unixadminschool.com

  • Home
  • Announcements
    • Feed
    • MISC
  • Beginners zone
    • Beginners Lessons
    • Career Guidance
  • Experts Zone
    • Cloud Computing
    • Configuration Solutions
    • Migrations
    • Network Design
    • Scripting
    • Server Security
    • SUN CLUSTERS
    • SUN LDOMS
    • Tools & Applications
    • Veritas Cluster Services ( VCS ) Learning
  • Intermediate Zone
    • Linux Learning
      • Linux Booting
      • Linux Disk Management
      • Linux LVM
      • Linux Networking
      • Linux Performance
      • Linux Troubleshooting
      • Linux YUM/RPM
      • Performance Analysis
      • Redhat Linux Kernel
      • RHEL 6
        • RHEL LDAP
        • Rhel6 Storage
      • Web Servers
    • Solaris Admin
      • Blog for Unix Admin
        • Storage Administration – SAN
      • Oracle Hardware
      • Reference Docs
      • Solaris 10 Zones & LDOMs
      • Solaris 11
      • Solaris Access Control
      • Solaris Best Practices
      • Solaris Booting
      • Solaris Disk Management
      • Solaris DNS
      • Solaris How-to
      • Solaris Installation
      • Solaris Kernel
      • Solaris Networking
      • Solaris NFS
      • Solaris NIS
      • Solaris Packages & Patching
      • Solaris Performance
      • Solaris Tips
      • Solaris Troubleshooting
      • Solaris User Authentication
      • solaris X86
      • Solaris ZFS and Boot Environment
      • Storage Configurations
      • SUN Hardware
      • Troubleshooting Flow charts
    • Veritas Admin
      • Veritas Netbackup
      • VxVM Learning
      • VxVM Troubleshooting
  • QUIZ Center
  • Vlabs

Subscribe

VxVM Troubleshooting – Increasing the Size of Veritas Disk Private Region

 

We know that each disk under veritas volume manager  is having some  identification information in it’s private region, so that the disks are readily identifiable irrespective of the machine they are connected.  When we place these disks under Veritas Diskgroups, the VxVM will start writing it’s configuration information to the same tiny private region. 

 

Unfortunately, the size of the private region is set at disk initialization and fixed for the life time of the disk. Whereas the configuration database , that stores volume,plex and subdisks definition  will continuously grow based on the configuration change we make.  If the private region is too small, then there will be some situations where the private region go full and won’t allow any  more configuration database updates in that disk group.  And there is no direct solution to increase the priviate region and normally we do follow this offline procedure to increase the private region length

 

1. Backup All data to tape

2. Re-initialize disks with larger private region

3. Recreate volumes as per the original configuration

4. Restore the data.

 

And just for an experiment , I have followed the below procedure  to increase  the private region without bringing the volumes down and the experiment went well. Here is the  result of the work I have done

  Full Story

Ramdev
5 Comments

Storage Operations – VxVM vs RHEL LVM2

 

Storage Operation

VXVM

RHEL LVM2

Installation and Configuration

Installed using Veritas installer

Installed as part of standard build via rpm

Scan for new devices

# vxdctl enable

# vgscan

Print list of volumes

# vxprint -v

# lvdisplay -C

Print current config (detailed)

# vxdg list

# vgdisplay

 

list volume group information

display volume group information

 

# vxdisk list

# pvdisplay

 

list disk information

display physical disk information

 

# vxprint -l

# lvdisplay

 

display detailed volume information

display logical volume information

Create new volume group

# vxdg init GROUP01 DISK01

# pvcreate /dev/mapper/mpath0

 

create diskgroup GROUP01 with device DISK01

# vgcreate GROUP01 /dev/mapper/mpath0

 

 

first initialise disk for LVM use, then create group GROUP1 on that disk

 

   

Full Story

Ramdev
10 Comments

Volume manager Migration from LVM to VxVM in Linux – Part 1

We all know that storage is key requirement for any server environment and the requirement for storage is always dynamic in nature. When we talk about the cost, providing highly redundant storage to each server is most expensive task for any organization and no company want to waste the storage with fixed allocation to each server. And  Companies  had huge requirement for the applications which has capability to dynamically add or reduce storage to the servers without affecting the operations.  And this requirement increased the demand for user friendly and effective volume manager tools.  Both the Operating System Vendors and third party vendors started providing volume manager tools to the industry, and below are some of the major Volume manager tools in place right now:

  • Solaris native Volume manager tools – SVM  and ZFS
  • Linux  native volume manager tools – LVM
  • Symantic native volume manager tools  – VxVM Full Story

Ramdev
11 Comments
Tagged with: [ linux vxvm, SAN configuration, storage migration, veritas learning, VxVM Learning ]

Quick Reference for Veritas Volume Manager Volume States and Plex States

 

 

While Troubleshooting Veritas Volume Manager, Understanding volume and plex states is key part to investigate about the current issue related to the Veritas Volumes. In this post, I made little effort to write all the possible Volume and Plex states so that it can be readily useful for others ( including me) for the day to day operations. This information is already available in internet in various formats, what I exactly tried here is just a consolidation,  for quick reference.

 

  Full Story

Ramdev
2 Comments

VxVM 5.0- Replacing rootdisk from rootdg – failing with error "Disk public region is too small"

Error while adding  replaced disk to the root mirror

Solaris:/etc/vx/bin> vxdg -g rootdg -k adddisk rootdisk=c1t4d0s2

VxVM vxdg ERROR V-5-1-10127 associating disk-media rootdisk with c1t4d0s2:    Disk public region is too small

 

Resolution: 

Solaris :/etc/vx/bin> vxdisk list

  • DEVICE       TYPE            DISK         GROUP        STATUS
  • c1t4d0s2     auto:sliced     -            -            online                   replaced disk
  • c2t0d0s2     auto:none       -            -            online invalid
  • c2t1d0s2     auto:sliced     localdg01    localdg      online
  • c2t2d0s2     auto:sliced     rootmirror   rootdg       online nohotuse   existing root mirror
  • c2t3d0s2     auto:sliced     localdg02    localdg      online
  • c2t5d0s2     auto:sliced     -            -            online
  • c3t176d0s2   auto:sliced     loachdg73    loachdg      online
  • c3t176d1s2   auto:sliced     loachdg74    loachdg      online
  • c3t176d2s2   auto:sliced     loachdg75    loachdg      online
  • c3t176d3s2   auto:sliced     loachdg76    loachdg      online
  • c3t176d4s2   auto:sliced     loachdg77    loachdg      online
  • c3t176d5s2   auto:sliced     loachdg78    loachdg      online
  • c3t176d6s2   auto:sliced     loachdg79    loachdg      online
  • c3t176d7s2   auto:sliced     loachdg80    loachdg      online
  • c3t176d63s2  auto:sliced     loachdg61    loachdg      online
  • c3t176d64s2  auto:sliced     loachdg62    loachdg      online
  • c3t176d65s2  auto:sliced     loachdg63    loachdg      online
  • c3t176d66s2  auto:sliced     loachdg64    loachdg      online
  • c3t176d67s2  auto:sliced     loachdg65    loachdg      online
  • c3t176d68s2  auto:sliced     loachdg66    loachdg      online
  • c3t176d69s2  auto:sliced     loachdg67    loachdg      online
  • c3t176d70s2  auto:sliced     loachdg68    loachdg      online
  • c3t176d71s2  auto:sliced     loachdg69    loachdg      online
  • c3t176d72s2  auto:sliced     loachdg70    loachdg      online
  • c3t176d73s2  auto:sliced     loachdg71    loachdg      online
  • c3t176d74s2  auto:sliced     loachdg72    loachdg      online Full Story

Ramdev
16 Comments
Tagged with: [ failure, repair, replacement, root disk, rootdg, Volume manager, VxVM Learning ]

VxVM : Re-adding a failed boot disk – incase of correctable errors

 

Re-adding a disk is same procedure as replacing a failed disk, except we use same disk. We have to detach the disk  from vxvm, so that the VxVM will detect the disk failure and will cease access to the failed disk.

 You can then perform any special procedures to correct the problem, such as reformatting the device. To re-add a failed boot disk

      1. Select the vxdiskadm “Replace a failed or removed disk”menuitem to replace the disk, and specify the same device as the replacement. For example, you might replace disk01 with the device c0t0d0s2.
      2.  If hot-relocation is enabled when a mirrored boot disk fails, an attempt is made to create a new mirror and remove the failed subdisks from the failing boot disk. If a re-add succeeds after a successful hot-relocation, the root and other volumes affected by the disk failure no longer exist on the re-added disk. Run vxunreloc to move the hot-relocated subdisks back to the newly replaced disk

Ramdev
Comment
Tagged with: [ boot disk, failed disk, recovery, replacement, vxvm troubleshoting ]
Pages1 2 3 4

  • About Author : My name is Ramkumar Ramadevu ( Ramdev ). I have started writing about enterprise unix system administration since 2009 just for my own knowledge reference, and then later I have made this site available for everyone, for better purpose. ... read more

  • Advertise Here Your Video Ad Here
  • Recent Comments

    • Ramdev commented :: Rahul, welcome to unixadminschool.Thanks for the message....
    • Rahul commented :: Awesome Ram, i came to know about this Blog 2 days and go through a...
    • Ramdev commented :: Hi Prajwala, I am glad that you like it :)...
    • Ramdev commented :: Pavan, the below command mentioned in this doc to show how much pemlen...
    • Ramdev commented :: pleae try      --             share -F nfs -o rw=oracle:root /filesyst...
    • Ramdev commented :: Hi Jack, the cfgadm you have to do it anyway to  make sure the disk i...
    • Maniswara Pavan commented :: Nice Post .........
    • Maniswara Pavan commented :: Hi Ram, I have a doubt here .. Lets think we have disk and its pr...
    • jack commented :: Do we need to initialize and configure the replaced disk in this proce...
    • Laxxi commented :: Hi Ram, Please guide me how can I provide Read write access to a Fs...
  • Latest Posts

    • Virtual Lab : Get Your hands dirty with grep & RegEx
    • Quiz – Redhat Linux Intermediate Skills
    • Solaris Quiz – Managing Filesystems and Disk Devices
    • Test Your Understanding about Linux Fundamentals
    • Solaris Quiz – System Startup and Shutdown
    • Solaris Quiz – Software Management
    • RHEL 6 – ISCSI Administration Series – ISCSI Lun resize
    • RHEL 6 – ISCSI Administration Series – Configuring ISCSI Server and Client
    • SAN Storage Migration – Solaris with VxVM
    • RHEL 6.3 – LDAP Series – Part 4 : Troubleshooting
    • RHEL 6.3 – LDAP Series – Part 3 : LDAP Configuration With Encrypted Communication using TLS/SSL
    • RHEL 6.3 – LDAP Series – Part 2 : Configuration of Certification Authority for LDAP encryption.
    • RHEL 6.3 – LDAP Series – Part 1 : Implementation of LDAP Authentication
    • [ Updated with Analysis ] – Finding the Linux Performance Bottleneck !!!
    • VxVM Troubleshooting – Increasing the Size of Veritas Disk Private Region
    • Virtualization for Unix Administrators
    • VCS Learning – I/O Fencing In action [ Video ]
    • VCS Learning : Learn about Cluster Hearbeats
    • Happy New Year 2013, Thank You. >
    • Storage Operations – VxVM vs RHEL LVM2
    • Veritas Netbackup : Unable to detect Robot from master server after Veritas Netbackup upgrade to 7.1.0.4.
    • A tool that changes the way of system administration – PUPPET ( from puppetlabs)
    • Redhat Enterprise Linux : Yum Quick Reference
    • Redhat Enterprise Linux – Network Bonding – Quick Reference ( RHEL5 / RHEL6)
    • Redhat Enterprise Linux Networking Troubleshooting – Quick Reference
    • RedHat Linux Grub Loader – FAQ and Quick Reference
    • Redhat Linux LVM – FAQ & Quick Reference
    • RedHat Linux Kernel – FAQ and Quick Reference
    • Solaris host level SAN migration from Clariion to VMAX – Hands on Lab
    • Linux Samba Server integration with Windows Active Directory – Part 2
  • Site Members

    • Log in
Copyright © 2009 unixadminschool.com. All rights reserved.