10 More Discussions You Might Find Interesting
1. AIX
Good afternoon!
Help with a solution
I have AIX 7.1
works through vios
I expanded Lun
that it is necessary to make that aix saw this change and to expand the section lvm
Sorry for my English (1 Reply)
Discussion started by: iformats
1 Replies
2. Solaris
Hi All
I am having VxVm on two Solaris hosts. host1 is using disk group dgHR. right now this server went down due to hardware fault. Not I need to import this dgHR into host2 server. Please let me know the procedure for the same. (1 Reply)
Discussion started by: amity
1 Replies
3. Solaris
Dear all,
i want to get the LUN ID for some disks in solaris 10
what commands options for the MPXIO and inq i want these utilities only
because i don't have solution enabler or powerpath
BR, (1 Reply)
Discussion started by: maxim42
1 Replies
4. AIX
Hi,
I am not getiting lun id information on VIO Server. I have used the command fget_config command.
just showing # prompt.
I would like know wheather any other command is there equiv of fget_config
which will display lun id? (4 Replies)
Discussion started by: manoj.solaris
4 Replies
5. Solaris
How to share a diskgroup in veritas. (1 Reply)
Discussion started by: padmaja
1 Replies
6. Solaris
I have a list of LUN ID, my task is to find if disk has been added or not. How do I do that? I have been searching the forum and not able to find answer.
thanks (4 Replies)
Discussion started by: uuontario
4 Replies
7. Solaris
hey guys i got this in my logs what does this mean: (1 Reply)
Discussion started by: sbn
1 Replies
8. Solaris
Hello experts..
I am unable to import a disk group using vxdg . Is there any other command to import a disk group..
Thanks in advance.. (4 Replies)
Discussion started by: younus_syed
4 Replies
9. AIX
I have been ask to write a script to show what phyical disks are linked to what luns. By host name. I was hoping someone had some ideas on how to do this. I am from a linux background and am struggling a bit here...lol...I have been given one command to help me out....lsmap..Anyhelp would be... (3 Replies)
Discussion started by: jameszak
3 Replies
10. Red Hat
Hello,
I'm trying to help a guy out on a VMWARE server, running what looks like a cut down version of redhat? 2.4.9-vmnix2 ...
Bascially the box serves vm clients via allocating a LUN from a SAN.. to cut a long story short, I need to find out which SAN the luns are comming from (could be 1... (0 Replies)
Discussion started by: itsupplies
0 Replies
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 also
lvm(8), lvcreate(8)
AUTHOR
Heinz Mauelshagen <Linux-LVM@Sistina.com>
Heinz Mauelshagen LVM TOOLS VGIMPORT(8)