10 More Discussions You Might Find Interesting
1. Solaris
Hi,
When we are running fsck in vxvm FS within few sec it will completed even if data is more than 500GB or in TB also.
compare to UFS FS in that it will take more time compare with vxvm.UFS check FS in block level. & then vvxm on where its checking the FS.
Please explain. (1 Reply)
Discussion started by: tiger09
1 Replies
2. Emergency UNIX and Linux Support
I have VxVM 5.1 running on Solaris-10. I have to increase a application file-system and storage team gave me a lun. After scanning scsi port by cfgadm, I can see them in format output. I labelled it, but I am not able to see them in "vxdisk list".
I already tried commands -->
vxdctl enable... (4 Replies)
Discussion started by: solaris_1977
4 Replies
3. Solaris
hi all,
how can we check whether vxvm is installed in our system or not in solaris?
Thanks in advance
dinu (4 Replies)
Discussion started by: dinu
4 Replies
4. Solaris
Anyone knows that how many volumes can be created in a Diskgroup?
Thanks in advance... (1 Reply)
Discussion started by: bpsunadm
1 Replies
5. Solaris
Hi community,
I've a hard question for you.
1)What are the differences between ZFS and Veritas Volume Manager on Solaris10?
2) what is the difference to manage the internal disks (Mirror)?
3) what is the difference to manage the external disks?
4) What is the difference to manage... (5 Replies)
Discussion started by: Sunb3
5 Replies
6. Filesystems, Disks and Memory
:confused:
Last week I read that VxVM won't work with MPxIO (i don't recall the link) and that it should be unconfigured when installing VxVM. Today I read that VxVM works in "pass-thru" mode with MPxIO and DMP uses the devices presented by MPxIO.
If I create disks with MPxIO and use VxVM to... (1 Reply)
Discussion started by: bluescreen
1 Replies
7. Solaris
Hi,
Quick question if anyone knows this. Is there a command I can use in Veritas Volume manager on Solaris that will tell me what the name of the SAN I am connected to? We have a number of SANs so I am unsure which one my servers are connected to. Thanks. (13 Replies)
Discussion started by: gwhelan
13 Replies
8. Solaris
DEVICE TYPE DISK GROUP STATUS
c0t0d0s2 sliced rootdisk rootdg online
c1t1d0s2 sliced disk01 rootdg online
c2t0d0s2 sliced actsvr101 actsvr1dg online
c2t2d0s2 sliced actsvr102 actsvr1dg online
c2t3d0s2 ... (13 Replies)
Discussion started by: incredible
13 Replies
9. Filesystems, Disks and Memory
I've got a Linux box that I'm pretty sure is having some disk issues. iostat isn't installed, but vmstat is, so i've been trying to use that to do some initial diagnostics while I go through our company's change control process to get iostat installed.
The problem I'm having is that the disks... (4 Replies)
Discussion started by: kknigga
4 Replies
10. Solaris
All solaris rescue gurus out there ....
I've a Solaris 2.6 E450 on which my sysadmin guy has deleted every file (not sub-directories) from the /etc directory.
The machine is (was) running Vxvm with the root volume encapsulated.
I've tried booting from CDROM, mounting the root volume... (3 Replies)
Discussion started by: andy11983
3 Replies
LEARN ABOUT HPUX
vxrootmir
vxrootmir(1M) vxrootmir(1M)
NAME
vxrootmir - create a mirror of a Veritas Volume Manager root disk
SYNOPSIS
/etc/vx/bin/vxrootmir [-g diskgroup] [-t tasktag]
[-p Pool_1,Pool_2,...]
[[-v] [-b] [-R] root_mirror]
DESCRIPTION
The vxrootmir command creates mirrors of all of the volumes on a Veritas Volume Manager (VxVM) rootable boot disk, and makes the new disk
bootable.
A disk to be used as a mirror can be specified either by its VM disk name (disk media name) or by its device name (disk access name).
If a disk media name is specified, it is validated to make sure that it exists and that it has been properly initialized. This validation
includes making sure that the private region is at the same location and has the same length as the private region on the primary root
disk, and that the sum of the lengths of all of the subdisks located on the primary root disk will fit within the available space in the
public region of the specified disk.
If a disk access name is specified, it is validated to make sure it exists and is not in use, and that the total length of all the subdisks
on the primary root disk will fit within the public region. The disk is then initialized to contain a private region with the same offset
and length as the private region on the primary root disk. A new disk media name is assigned to the disk formed from the prefix rootdisk
followed by the next available number (for example, rootdisk02, rootdisk03, and so on).
All volumes that have a subdisk on the primary VxVM root disk are mirrored on the specified disk. When the root volume (rootvol) is mir-
rored, the vxassist command executes vxbootsetup to set up the new disk as a boot disk.
The -p option allows you to mirror the volumes on the root disk as stripe columns across several disks. The argument to this option is a
list of disks that are to be used for the stripe column mirrors. If not enough disks are specified, vxrootmir prints a message to the
standard error output, including information on how many disks are required, and then exits. When initialized for VxVM use, these stripe
column disks are named with the prefix rootaux followed by the next available number (for example, rootaux01, rootaux02, and so on).
OPTIONS
-b If the system was booted from the VxVM root disk that is being mirrored, this option uses the setboot command to set the alter-
nate boot disk to the specified mirror. If the system was booted from another root disk (such as an LVM root disk), an alternate
root disk is not set. If the -v option is also specified, information is displayed on the current setboot settings, and on
whether the alternate boot disk is set to the specified mirror.
-g diskgroup
Specifies the boot disk group.
-p Pool_1,Pool_2,...
Specifies the disks that are to be used for stripe column targets when mirroring the VxVM root disk. The disks can be specified
either as disk access names, or as disk media names if they have previously been initialized for use with VxVM. If specified as
disk access names, the disks are checked for existence, correct size, and availability for use.
-R Indicates that only the volumes required to boot successfully from the new mirror are to be mirrored.
-t tasktag
Marks any tasks that are registered to track the progress of an operation with the tag tasktag. This option is passed to vxas-
sist when mirroring volumes, so any child tasks are also tagged with tasktag.
-v Displays verbose output including timestamps for operations in progress. This option is useful as mirroring large volumes can
take a long time.
ARGUMENTS
daname Specifies the disk to be used as a mirror by its disk access name (such as c0t2d0).
dmname Specifies the disk to be used as a mirror by its disk media name (such as rootdisk03).
EXAMPLES
This example shows the vxrootmir command being invoked in its simpliest form:
/etc/vx/bin/vxrootmir c5t1d0
The next example shows how to use the -R option with vxrootmir.
# /etc/vx/bin/vxrootmir -v -b -R c5t10d0
vxrootmir: 10:10:
Gathering information on the current VxVM root configuration
vxrootmir: 10:10: Checking specified disk(s) for usability
vxrootmir: 10:10: Preparing disk c5t10d0 as a VxVM disk
vxrootmir: 10:10: Adding disk c5t10d0 to rootdg as rootdisk02
vxrootmir: 10:10: Mirroring only volumes required for root mirror boot
vxrootmir: 10:10: Mirroring volume standvol
vxrootmir: 10:11: Mirroring volume swapvol
vxrootmir: 10:18: Mirroring volume rootvol
vxrootmir: 10:20: Current setboot values:
vxrootmir: 10:20: Primary: 0/4/0/1.11.0
vxrootmir: 10:20: Alternate: 0/4/0/1.13.0
vxrootmir: 10:20: Making c5t10d0 (0/4/0/1.10.0) the alternate boot disk
vxrootmir: 10:20: Disk c5t10d0 is now a mirrored root disk
The final example shows how to specify a list of disks for use as stripe column mirrors:
# /etc/vx/bin/vxrootmir -v -p c5t11d0,c5t12d0,c5t13d0 c5t10d0
vxrootmir: 12:11:
Gathering information on the current VxVM root configuration
vxrootmir: 12:11: Checking specified disk(s) for usability
vxrootmir: 12:11: Preparing disk c5t10d0 as a VxVM disk
vxrootmir: 12:11: Adding disk c5t10d0 to rootdg as rootdisk02
vxrootmir: 12:11: Preparing disk c5t11d0 as a VxVM disk
vxrootmir: 12:11: Adding disk c5t11d0 to rootdg as DM rootstpm01
vxrootmir: 12:11: Preparing disk c5t12d0 as a VxVM disk
vxrootmir: 12:11: Adding disk c5t12d0 to rootdg as DM rootstpm02
vxrootmir: 12:11: Preparing disk c5t13d0 as a VxVM disk
vxrootmir: 12:11: Adding disk c5t13d0 to rootdg as DM rootstpm03
vxrootmir: 12:11: Mirroring all volumes on root disk
vxrootmir: 12:11: Mirroring volume standvol
vxrootmir: 12:12: Mirroring volume swapvol
vxrootmir: 12:19: Mirroring volume rootvol
vxrootmir: 12:21: Mirroring volume optvol
vxrootmir: 12:24: Mirroring volume usrvol
vxrootmir: 12:27: Mirroring volume homevol
vxrootmir: 12:28: Mirroring volume tmpvol
vxrootmir: 12:28: Mirroring volume varvol
vxrootmir: 12:36: Disk c5t10d0 is now a mirrored root disk
NOTES
If the vxrootmir command aborts for any reason, or if you interrupt the command during execution, an attempt is made to clean up the VxVM
objects that had been generated up to the time of the abort or interruption. All mirror plexes that had already been added, or that were
in the process of being added when the interruption occurred, are removed. All Data Media (DM) objects that were created are also removed.
If a plex or a DM object cannot be removed, an explanatory message is displayed.
SEE ALSO
setboot(1M), vxassist(1M), vxbootsetup(1M), vxintro(1M), vxmirror(1M), vxtask(1M)
VxVM 5.0.31.1 24 Mar 2008 vxrootmir(1M)