Explore topic-wise InterviewSolutions in .

A disk which has FAILED can be SEEN from the output of vxdisk list command. The disk device ctd will be missing from the output and it can be seen as failed was: c#t#d#. This confirms that the disk has indeed failed.

We can use vxdiskadd menu OPTIONS to REPLACE the faulted disk. Choose option 5 from the men, and then list the failed disk using 'list' option. We would have to choose an alternate disk for the replacement. The list of available disks is also shown by vxdiskadd. Press 'y' and complete the replacement activity.

A disk which has failed can be seen from the output of vxdisk list command. The disk device ctd will be missing from the output and it can be seen as failed was: c#t#d#. This confirms that the disk has indeed failed.

We can use vxdiskadd menu options to replace the faulted disk. Choose option 5 from the men, and then list the failed disk using 'list' option. We would have to choose an alternate disk for the replacement. The list of available disks is also shown by vxdiskadd. Press 'y' and complete the replacement activity.

Yes, If some of the DISKS in a Diskgroup have failed, you can IMPORT the DG USING –f option 

# Vxdg –c import diskgroup

Yes, If some of the disks in a Diskgroup have failed, you can import the DG using –f option 

# Vxdg –c import diskgroup

The private region of a VxVM disk stored disk header LABEL and configuration information about VxVM objects such as VOLUMES, plexes and SUB disks.

Yes, each disk in a diskgroup STORES an entire copy of the configuration information.

The private region of a VxVM disk stored disk header label and configuration information about VxVM objects such as volumes, plexes and sub disks.

Yes, each disk in a diskgroup stores an entire copy of the configuration information.

The DG configuration info is STORED in /etc/vx/cbr/bk directory. Last 5 configuration CHANGES are stored.

The DG configuration info is stored in /etc/vx/cbr/bk directory. Last 5 configuration changes are stored.

• Vxconfigd daemon handles all configuration management tasks for VxVM OBJECTS. It MAINTAINS disk and disk group configuration details, communicates configuration changes to the KERNEL, and modifies the persistent configuration information stored on disks.
• Vxconfigd provides the interface between VxVM commands and the kernel device drivers.
• Vxconfigd handles configuration change requests from VxVM utilities, communicates the change requests to the VxVM kernel, and modifies configuration information stored on disk.
• Vxconfigd also initializes VxVM when the SYSTEM is booted.
• So PRACTICALLY any command which changes the configuration of VxVM objects (plexes, volumes) interact with vxconfigd daemon.

There are a few risks and issues involved while reducing a FILESYSTEM in VxVM.

• UFS volumes cannot be SHRUNK, only grow operation is permitted.
• VxFS volumes must be MOUNTED for grow and shrink operation; if it is unmounted no operation can be performed
• You cannot resize a volume that contains plexes with different LAYOUT types (e.g concat and stripe). Attempting to do so results in the following error message:

VxVM vxresize ERROR V-5-1-2536 Volume has different

Organization in each mirror 

To resize such a volume successfully, you must FIRST reconfigure it so that each data plex has the same layout type.

There are a few risks and issues involved while reducing a Filesystem in VxVM.

VxVM vxresize ERROR V-5-1-2536 Volume has different

Organization in each mirror 

To resize such a volume successfully, you must first reconfigure it so that each data plex has the same layout type.

If you FACED this issue because of fabric disconnection then simply do vxdisk scandisks, otherwise unset up the DISK using /etc/vx/bin/vxdisksetup and setup the DISKS again using /etc/vx/bin/vxdisksetup, this will definitely help! [ /etc/vx/bin/vxdisksetup will REMOVE the private region from the disk and destroys data, backup the data before using this OPTION]

If you faced this issue because of fabric disconnection then simply do vxdisk scandisks, otherwise unset up the disk using /etc/vx/bin/vxdisksetup and setup the disks again using /etc/vx/bin/vxdisksetup, this will definitely help! [ /etc/vx/bin/vxdisksetup will remove the private region from the disk and destroys data, backup the data before using this option]

Private region stores the STRUCTURED VxVM INFORMATION; it also stores the disk ID and disk GEOMETRY. In short words it has METADATA of the disk.

Private region stores the structured VxVM information; it also stores the disk ID and disk geometry. In short words it has metadata of the disk.

vxdisk LIST is the COMMAND will list the disks from the DG which is CURRENTLY imported; you can CHECK the same using vxprint command too. Vxdisk -o alldgs list command list all the disks which are in DIFFERENT dg's.

vxdisk list is the command will list the disks from the DG which is currently imported; you can check the same using vxprint command too. Vxdisk -o alldgs list command list all the disks which are in different dg's.

You can USE /etc/vx/bin/vxdisksetup to UNSET up the DISK, and /etc/vx/vxdisksetup to SETUP the disk.

You can use /etc/vx/bin/vxdisksetup to unset up the disk, and /etc/vx/vxdisksetup to setup the disk.

vxassist command is used to do all volume administration; following is the DESCRIPTION and syntax.

Grow by OPTION: This is will grow your file system by adding new SIZE to the existing file system.

Grow to option: This will grow your file system as per the new size. This WILL NOT ADD new size to the existing one.

Shrink by option: This will shrink your file system by REDUCING new size from existing file system.

Shrinkto option: This will shrink your file system as per the new size. This WILL NOT REDUCE the file system by reducing new size.

Command: vxassist -g [growto, growby, shrinkto, shrink by] length

vxassist command is used to do all volume administration; following is the description and syntax.

Grow by option: This is will grow your file system by adding new size to the existing file system.

Grow to option: This will grow your file system as per the new size. This WILL NOT ADD new size to the existing one.

Shrink by option: This will shrink your file system by reducing new size from existing file system.

Shrinkto option: This will shrink your file system as per the new size. This WILL NOT REDUCE the file system by reducing new size.

Command: vxassist -g [growto, growby, shrinkto, shrink by] length

RUN vxdisk ADD command, which will open menu driven program to do VARIOUS DISK operations, select add DISKS option or you can use another command vxdisk add.

Run vxdisk add command, which will open menu driven program to do various disk operations, select add disks option or you can use another command vxdisk add.

PRIVATE DG: The DG which is only visible for the host on which you have created it, if the host is a part of CLUSTER, the private DG will not be visible to the other cluster nodes.

SHARED DG: The DG which is shareable and visible to the other cluster nodes.

Private DG: The DG which is only visible for the host on which you have created it, if the host is a part of cluster, the private DG will not be visible to the other cluster nodes.

Shared DG: The DG which is shareable and visible to the other cluster nodes.

MIRROR, STRIPED, concat (DEFAULT one), RAID 5, stripe-mirror, mirror-stripe.

Mirror, striped, concat (default one), raid 5, stripe-mirror, mirror-stripe.

For Private DG Command: vxdg INIT

For SHARED DG Command: vxdg -s init < DISK1 disk2 disk3 &GT;

For Private DG Command: vxdg init

For Shared DG Command: vxdg -s init < disk1 disk2 disk3 >

Rootvg is the MANDATORY diskgroup in VXVM 3.5, install is the command to configure VxVM, It will CREATE the disk GROUPS, initializes the disks and adds them to the GROUP.

Rootvg is the mandatory diskgroup in VxVM 3.5, install is the command to configure VxVM, It will create the disk groups, initializes the disks and adds them to the group.

# vxdg UPGRADE &LT;DISK GROUP&GT;

It will upgrade the DG to the highest DG version supported by VxVM.

# vxdg upgrade <disk group>

It will upgrade the DG to the highest DG version supported by VxVM.

# vxdg DESTROY &LT;DISK GROUP&GT;

# vxdg destroy <disk group>

# vxdg join &LT;source DG&GT; <TARGET DG>

# vxdg join <source DG> <target DG>

# vxdg –o expand SPLIT &LT;OLD DG> <new DG> disk01 disk02

It will CREATE a new DG with two specified disks.

# vxdg –o expand split <old DG> <new DG> disk01 disk02

It will create a new DG with two specified disks.

# vxdg –o EXPAND move

# vxdg –o expand move datadg newdata dg disk01

It will move the ENTIRE ASSOCIATED OBJECT with disk02 from datadog to NEW datadog.

# vxdg –o expand move

# vxdg –o expand move datadg newdata dg disk01

It will move the entire associated object with disk02 from datadog to new datadog.

# vxdg –f IMPORT &LT;DISK GROUP&GT;

# vxdg –f import <disk group>

# vxdg –C IMPORT &LT;DISK GROUP&GT;

# vxdg –C import <disk group>

# vxdg –n <NEW DISK GROUP> DEPORT <disk group>

# vxdg –n <new disk group> deport <disk group>

# vxdg –t –n <new DISK GROUP&GT; IMPORT <disk group>

# vxdg –t –n <new disk group> import <disk group>

# vxdg DEPORT &LT;DISK GROUP&GT;

# vxdg deport <disk group>

First you must KNOW the DG ID of the destroyed disk group name. You can get the DG ID by displaying the INCLUDED disk of destroyed DG.

# vxdg IMPORT &LT;DG ID>

First you must know the DG ID of the destroyed disk group name. You can get the DG ID by displaying the included disk of destroyed DG.

# vxdg import <DG ID>

# vxdg IMPORT &LT;DISK GROUP&GT;

# vxdg import <disk group>

# vxdg –g SET &LT;DISKGROUP&GT; cds=on|off

# vxdg –g set <diskgroup> cds=on|off

# vxdg –G <DG VERSION&GT; INIT <disk GROUP>

# vxdg –G <DG version> init <disk group>

# vxdg INIT &LT;DISK GROUP&GT; cds=on|off

# vxdg init <disk group> cds=on|off

# vxdg FREE or # vxdg –g free

# vxdg free or # vxdg –g free

# vxdg LIST or # vxdg list &LT;DISK GROUP&GT;

# vxdg list or # vxdg list <disk group>

# vxdctl DEFAULT &LT;DISK GROUP&GT;

# vxdctl default <disk group>

#vxdg DEFAULTS

#vxdg defaults

# vxedit SET user=ip group=eigrp mode=0666 VG01

# vxedit set user=ip group=eigrp mode=0666 vg01

# vxedit SET COMMENT “COMMENTS are here” subdisk 01-01

# vxedit set comment “comments are here” subdisk 01-01

# vxedit -G HOMEDG SET spare=on disk90

# vxedit -g homedg set spare=on disk90

# vxedit -G ROOTDG RENAME disk90 DISK80

# vxedit -g rootdg rename disk90 disk80

# vxedit -RF RM VOLUME NAME

# vxedit -rf rm volume name

To add or BRING a disk under VERITAS Volume MANAGER control:

# vxdiskadd c0t0d1 or # vxdisksetup -i c0t0d1

It might help to NEWFS the s2 slice of the disk and perform a vxdctl ENABLE to get it to add a disk.

To add or bring a disk under Veritas Volume Manager control:

# vxdiskadd c0t0d1 or # vxdisksetup -i c0t0d1

It might help to newfs the s2 slice of the disk and perform a vxdctl enable to get it to add a disk.

# vxdisk RM c0t0d0

# vxdisk rm c0t0d0

# vxdisk RM DISK 01

# vxdisk rm disk 01

# vxdisk LIST

# vxdisk list

# vxdisk clearimport c0t0d0s0

# vxdisk clearimport c0t0d0s0

To remove a DISK, disk90, from a disk group, homedg, in Veritas VOLUME Manager:

# vxdg -g homedg rmdisk disk90

To remove a disk, disk90, from a disk group, homedg, in Veritas Volume Manager:

# vxdg -g homedg rmdisk disk90

To ADD the PHYSICAL disk c0t0d0 in the disk group HOMEDG calling it disk90 in VERITAS in Volume Manager:

# vxdg -g homedg adddisk disk90=c0t0d0

To add the physical disk c0t0d0 in the disk group homedg calling it disk90 in Veritas in Volume Manager:

# vxdg -g homedg adddisk disk90=c0t0d0