10 More Discussions You Might Find Interesting
1. UNIX for Beginners Questions & Answers
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
2. HP-UX
Hello all,
So I made a rookie mistake today. I forgot to remove my disk from my disk group, before running the following command:for i in `ioscan -fnN | awk /NO/'{print $3}'`
do
rmsf -H $i
done
I am trying to run the following command, but not having any luck obviously:vxdg -g dgvol1 rmdisk... (0 Replies)
Discussion started by: mrkejames2
0 Replies
3. Shell Programming and Scripting
Hi Experts
I need an script to add an disk in to the veritas volume manager disk group.
For example:
# cd /tmp
# view disk
c6t5d2
c6t2d1
c6t3d7
c6t11d2
c7t11d2
c6t11d6
Normally we add the disk like this:
# vxdg -g freedg freedisk01=c6t5d2
# vxdg -g freedg freedisk02=c6t2d1
#... (3 Replies)
Discussion started by: indrajit_preet
3 Replies
4. Solaris
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)
Discussion started by: buggin
0 Replies
5. Solaris
I am looking forward to configure Veritas DMP on Solaris-10.
All pointers appreciated.
Thanks, (3 Replies)
Discussion started by: menonk
3 Replies
6. UNIX and Linux Applications
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)
Discussion started by: jm6601
0 Replies
7. Solaris
Previously , i remove the disk by
#vxdg -g testdg -k rmdisk testdg02
But i got error when i -k adddisk
bash-2.03# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c0t0d0s2 auto:none - - online invalid
c0t1d0s2 auto:none ... (1 Reply)
Discussion started by: waibabe
1 Replies
8. Solaris
I have a bogus disk that keeps showing up as failed from vxdisk list
- - disk hpdg failed was:c2t0d11s2
There isnt any c2 devices on the system:
# ls /dev/dsk/c2*
/dev/dsk/c2*: No such file or directory
# ls /dev/rdsk/c2*
/dev/rdsk/c2*: No such file or... (3 Replies)
Discussion started by: kiem
3 Replies
9. Solaris
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)
Discussion started by: Jartan
10 Replies
10. Filesystems, Disks and Memory
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)
Discussion started by: ozzmosiz
2 Replies
LEARN ABOUT OSF1
volrecover
volrecover(8) System Manager's Manual volrecover(8)
NAME
volrecover - Performs volume recovery operations
SYNOPSIS
/sbin/volrecover [-g diskgroup] [-sb] [-o options] [volume | medianame...]
OPTIONS
Options that can be specified to volrecover are: Starts disabled volumes that are selected by the operation. Volumes will be started
before any other recovery actions are taken. Volumes will be started with the -o delayrecover start option. This requests that any opera-
tions that can be delayed in starting a volume will be delayed. In other words, only those operations necessary to make a volume available
for use will occur. Other operations, such as mirror resynchronization, attaching of stale plexes and subdisks, and recovery of stale RAID5
parity will normally be delayed. Performs recovery operations in the background. With this option, volrecover will put itself in the back-
ground to attach stale plexes and subdisks, and to resynchronize mirrored volumes and RAID5 parity. If this is used with -s, volumes will
be started before recovery begins in the background. Performs no recovery operations. If used with -s, volumes will be started, but no
other actions will be taken. If used with -p, the only action of volrecover will be to print a list of startable volumes. Prints the list
of selected volumes that are startable. For each startable volume, a line is printed containing the following information: the volume name,
the disk group ID of the volume, the volume's usage type, and a list of state flags pertaining to mirrors of the volume.
State flags and their meanings are: One of the mirrors was detached by an I/O failure One of the mirrors needs recovery, but the
recovery is related to an administrative operation, not an I/O failure Neither kdetach nor stale is appropriate for the volume.
Displays information about each task started by volrecover. For recovery operations (as opposed to start operations), a completion
status is printed when each task completes. Displays commands that volrecover would execute without actually executing them. Lim-
its operation of the command to the given disk group, as specified by disk group ID or disk group name. If no volume or medianame
operands are given, all disks in this disk group will be recovered; otherwise, the volume and medianame operands will be evaluated
relative to the given disk group.
Without the -g option, if no operands are given, all volumes in all imported disk groups will be recovered; otherwise, the disk
group for each medianame operand will be determined based on name uniqueness within all disk groups. Passes the given option argu-
ments to the -o options for the volplex att and volume start operations generated by volrecover. An option argument of the form pre-
fix:options can be specified to restrict the set of commands that the -o option should be applied to.
Defined prefixes are: Applies to all invocations of the volume utility (volume starts, mirror resynchronizations, RAID5 partity
rebuilds, and RAID5 subdisk recoveries) Applies to all invocations of the volplex utility (currently used only for attaching plexes)
Applies specifically to plex attach operations applies specifically to volume start operations Applies to subdisk recoveries Applies
to mirror resynchronization and RAID5 parity recovery
DESCRIPTION
The volrecover program performs plex attach, RAID5 subdisk recovery, and resynchronize operations for the named volumes, or for volumes
residing on the named disks (medianame).
If no medianame or volume operands are specified, the operation applies to all volumes (or to all volumes in the specified disk group).
If -s is specified, disabled volumes will be started. With -s and -n, volumes are started, but no other recovery takes place.
Recovery operations will be started in an order that prevents two concurrent operations from involving the same disk. Operations that
involve unrelated disks will run in parallel.
EXAMPLES
To recover, in the background, any detached subdisks or plexes that resulted from replacement of a specified disk, use the command:
# volrecover -b medianame
If you want to monitor the operations, use the command:
# volrecover -v medianame
SEE ALSO
volintro(8), volplex(8), volume(8)
volrecover(8)