I've had a VXFS filesystem get corrupted and now it won't mount.
Can I run a fsck -y on the raw disk device or should something be
done within veritas? Veritas does not see the disk at the moment. (2 Replies)
Hi there,
My task is to replace the two 73 G disks with two 143 G disks , which has vxvm 4.1 running on it. I would like to know whether the steps iam following are correct.
1. Break the sub-disks, plexes of the root mirror.
2. Remove the sub-disks,plexes of the root mirror.
3. Remove one of... (10 Replies)
Hi, Does anyone have a clever way of mapping the following from two different files using perl.
sample line from vxdisk list output (vxdisk-list.file):
emcpower18s2 auto:sliced IDFAG1_1 (IDFAG1_appdg) online
sample line from 'inq' output (inq.file):
... (0 Replies)
I am trying to write a kornshell script that will automatically create veritas disk groups. However, the only utility that I can find that will create the diskgroup is vxdiskadd, which prompts with interactive questions. I've tried to pass the answers through to vxdiskadd, but I receive the... (0 Replies)
hi all
i am using vxvm 5.1 on my sun blade 150 which is running with solaris 5.10. When i give the command "vxdisk list" it gives the following output
# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c0t0d0s2 auto:none - - online... (2 Replies)
I installed new internal disks in my p570. They will be part of a new AIX vg. Unfortunately, we have Veritas Volume Manager running on this AIX 5.2 ml 10 box. Veritas has grabbed control of the disks. I want AIX LVM to control the disks.
I cannot get these disks free of Veritas:
<lspv... (2 Replies)
People i have an a storage i create two virtual disk 1 y 2.
In the virtual disk 1 i configure 8 volumes and in the Vd2 configure 5 volumes.
Now i want to create a disk group called Prod2 y Dev2 but when i go to vxdiskadm and i choose add disk o encapusalte when i press list to list the disk... (0 Replies)
Hi,
I`m on SunFire480R with Solaris 10. Disk in rootdg group failed, so it was replaced. However, I cannot make Veritas initalise the replaced disk:
# vxdctl enable
# vxdisk list c1t0d0s2
Device: c1t0d0s2
devicetag: c1t0d0
type: auto
flags: online error private autoconfig... (1 Reply)
Need help getting all disk devices back on node 2 the same as node 1.
Recently Veritas and/or Sun cluster got wrecked on my 2 node Sun cluster after installing the latest patch cluster. I backed out the patches and then node 2 could see only half of the devices and Veritas drives (though format... (0 Replies)
Hi Experts,
I wanted to extend a veritas file system which is running on veritas cluster and mounted on node2 system.
#hastatus -sum
-- System State Frozen
A node1 running 0
A node2 running 0
-- Group State
-- Group System Probed ... (1 Reply)
Discussion started by: Skmanojkum
1 Replies
LEARN ABOUT HPUX
vxdarestore
vxdarestore(1M)vxdarestore(1M)NAME
vxdarestore - restore simple or nopriv disk access records
SYNOPSIS
/etc/vx/bin/vxdarestore
DESCRIPTION
The vxdarestore utility is used to restore persistent simple or nopriv disk access (da) records that have failed due to changing the naming
scheme used by vxconfigd from c#t#d#-based to enclosure-based.
The use of vxdarestore is required if you use the vxdiskadm command to change from the c#t#d#-based to the enclosure-based naming scheme.
As a result, some existing persistent simple or nopriv disks go into the "error" state and the VxVM objects on those disks fail.
vxdarestore may be used to restore the disk access records that have failed. The utility also recovers the VxVM objects on the failed disk
access records.
Note: vxdarestore may only be run when vxconfigd is using the enclosure-based naming scheme.
Note: You can use the command vxdisk list da_name to discover whether a disk access record is persistent. The record is non-persistent if
the flags field includes the flag autoconfig; otherwise it is persistent.
The following sections describe how to use the vxdarestore utility under various conditions.
Persistent Simple/Nopriv Disks in the rootdg Disk Group
If all persistent simple or nopriv disks in the rootdg disk group go into the "error" state, use the following procedure:
1. Use the vxdiskadm command to change back to the c#t#d# based naming scheme.
2. Either shut down and reboot the host, or run the following command:
vxconfigd -kr reset
3. If you want to use the enclosure-based naming scheme, add a non-persistent simple disk to the rootdg disk group, use vxdiskadm to
change to the enclosure-based naming scheme, and then run vxdarestore.
Note: If not all the disks in rootdg go into the error state, simply running vxdarestore restores those disks in the error state and the
objects that that they contain.
Persistent Simple/Nopriv Disks in Disk Groups other than rootdg
If all disk access records in an imported disk group consist only of persistent simple and/or nopriv disks, the disk group is put in the
"online dgdisabled" state after changing to the enclosure-based naming scheme. For such disk groups, perform the following steps:
1. Deport the disk group using the following command:
vxdg deport diskgroup
2. Run the vxdarestore command.
3. Re-import the disk group using the following command:
vxdg import diskgroup
NOTES
Use of the vxdarestore command is not required in the following cases:
o If there are no persistent simple or nopriv disk access records on an HP-UX host.
o If all devices on which simple or nopriv disks are present are not automatically configurable by VxVM. For example, third-party
drivers export devices that are not automatically configured by VxVM. VxVM objects on simple/nopriv disks created from such disks
are not affected by switching to the enclosure based naming scheme.
The vxdarestore command does not handle the following cases:
o If the enclosure-based naming scheme is in use and the vxdmpadm command is used to change the name of an enclosure, the disk access
names of all devices in that enclosure are also changed. As a result, any persistent simple/nopriv disks in the enclosure are put
into the "error" state, and VxVM objects configured on those disks fail.
o If the enclosure-based naming scheme is in use and the system is rebooted after making hardware configuration changes to the host.
This may change the disk access names and cause some persistent simple/nopriv disks to be put into the "error" state.
o If the enclosure-based naming scheme is in use, the device discovery layer claims some disks under the JBOD category, and the vxdd-
ladm rmjbod command is used to remove remove support for the JBOD category for disks from a particular vendor. As a result of the
consequent name change, disks with persistent disk access records are put into the "error" state, and VxVM objects configured on
those disks fail.
EXIT CODES
A zero exit status is returned if the operation is successful or if no actions were necessary. An exit status of 1 is returned if vxdare-
store is run while vxconfigd is using the c#t#d# naming scheme. An exit status of 2 is returned if vxconfigd is not running.
SEE ALSO vxconfigd(1M), vxdg(1M), vxdisk(1M), vxdiskadm(1M), vxdmpadm(1M), vxintro(1M), vxreattach(1M), vxrecover(1M)VxVM 5.0.31.1 24 Mar 2008 vxdarestore(1M)