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)
I am trying to build a veritas volume similar to an existing volume on another server. The output on source server is:
usbtor12# vxprint -hrtg appdg
v anvil_sqlVOL - ENABLED ACTIVE 629145600 SELECT - fsgen
pl anvil_sqlVOL-01 anvil_sqlVOL ENABLED ACTIVE 629145600... (3 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)
I have a machine (5.10 Generic_142900-03 sun4u sparc SUNW,Sun-Fire-V210) that we are upgrading the storage and my task is to mirror what is already on the machine to the new disk. I have the disk, it is labeled and ready but I am not sure of the next steps to mirror the existing diskgroup and... (1 Reply)
Hi,
I have a 2 node Cluster. Which is working in active/passive mode (i.e Node#1 is running and when it goes down the Node#2 takes over)
Now there's this requirement that we need a mount point say /test that should be available in active node #1 and when node #1 goes down and node#2 takes... (6 Replies)
Good afternoon all,
I'll probably confuse everyone as I'm a Windows guy dealing with AIX 6.1 and can't quite figure out how to do something. I have a P520 server running 2 LPARs and we have an IVM (not HMC).Within the IVM under Virtual Storage Management, when I check the Physical Volumes, I have... (4 Replies)
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,
I want to create a volume group of 200 GB and then create different file systems on that.
please help me out. Its becomes confusing when the PP calculating PP.
I don't understand this concept. (2 Replies)
Hello Guys,
I want to create a file system dedicated for an application installation. But there is no space in volume group to create a new logical volume. There is enough space in other logical volume which is being mounted on /var.
I know we can use that logical volume and create a virtual... (2 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 REDHAT
vgimport
VGIMPORT(8) System Manager's Manual VGIMPORT(8)NAME
vgimport - make volume groups known to the system
SYNOPSIS
vgimport [-d|--debug] [-f|--force] [-h|--help] [-v|--verbose] VolumeGroupName PhysicalVolumePath [PhysicalVolumePath...]
DESCRIPTION
vgimport allows you to make a volume group known to the system which has previously been exported (see vgexport(8) ) on this or another
system.
OPTIONS
-d, --debug
Enables additional debugging output (if compiled with DEBUG).
-f, --force
Force import of volume group even though it is not flagged exported. This option allows the importing of volume groups from broken
systems.
-h, --help
Print a usage message on standard output and exit successfully.
-v, --verbose
Display verbose runtime information about vgimport's activities.
Examples
"vgimport myvg /dev/sd[b-h]5" tries to make new volume group "myvg" known to the system. The previously exported volume group (see vgex-
port(8) ) resides on disk partitions "/dev/sdb5" to "/dev/sdh5".
DIAGNOSTICS
vgimport returns an exit code of 0 for success and > 0 for error:
1 no volume group name on command line
2 invalid volume group name
3 no physical volume(s) on command line
4 volume group already exists
5 physical volume occurs mutiple times on command line
6 invalid physical volume name
7 error reading physical volume
8 physical volume is not exported
9 error reallocating memory
10 error allocating memory
11 no valid physical volumes found
12 physical volume belongs to a different exported volume group
13 wrong number of physical volumes
14 error reading VGDA from disk(s)
15 VGDA is inconsistent
16 invalid logical volume count
17 error getting a free volume group number
18 error writing VGDA to physical volumes
19 error creating VGDA in kernel
20 error inserting volume group into lvmtab
21 error doing backup of VGDA to disk
22 error storing VGDA in lvmtab
23 not enough free logical volume manager block specials available
95 driver/module not in kernel
96 invalid I/O protocol version
97 error locking logical volume manager
98 invalid lvmtab (run vgscan(8))
99 invalid command line
Example
"vgimport this_import /dev/sdk3 /dev/sdj4" tries to import a volume group contained on both partitions. The volume group this_import may
not already exit. You have to specify all physical volumes belonging to the exported volume group.
See alsolvm(8), lvcreate(8)AUTHOR
Heinz Mauelshagen <Linux-LVM@Sistina.com>
Heinz Mauelshagen LVM TOOLS VGIMPORT(8)