Sponsored Content
Operating Systems AIX Increase LUN size in AIX with VIOS and HACMP Post 302606562 by Vit0_Corleone on Monday 12th of March 2012 04:43:17 AM
Old 03-12-2012
I would try export and Import VG tor reread VGDA from the disks
 

10 More Discussions You Might Find Interesting

1. HP-UX

increase size

Hi All, one of the mount point in Hp ux server has reached 95% its a data base file and can not be deleted. so i want to know how to increase the size of mount point i am new to unix ,please help me (1 Reply)
Discussion started by: jyoti
1 Replies

2. AIX

HACMP LV size is not reflecting

Hi i increased the lv size using smit hacmp. but, the new size is not reflecting.. why?. the pp size is 512 MB. before it was 4 PP's. i increased to 10 PP's. when i type df -m /xxx.. it is showing 2GB only. see the info below.. root@db:/ > df -m /xxx/xxx Filesystem MB blocks Free... (2 Replies)
Discussion started by: honeym210
2 Replies

3. AIX

Problem mapping LUN disk from VIOS to the LPAR

Hello guys, It would be so nice of you if someone can provide me with these informations. 1) My SAN group assigned 51G of LUN space to the VIO server.I ran cfgdev to discover the newly added LUN. Unfortunately most of the disks that are in VIO server is 51G. How would I know which is the newly... (3 Replies)
Discussion started by: solaix14
3 Replies

4. UNIX for Dummies Questions & Answers

Increase salt size

Unix protect its password by using salt It that mean larger the salt size the more secure? if the salt size increase greatly, will the password still able to be cracked? thank you for helping (1 Reply)
Discussion started by: cryogen
1 Replies

5. Solaris

Largest LUN size in Solaris 10

What is the largest possible LUN size that can be presented to Solaris 10. I've been googling a lot about this. The new EFI lablels (an alternative to VTOC) supports LUNs greater than 2TB. I need to know the upper limit. please help me find it. (4 Replies)
Discussion started by: pingmeback
4 Replies

6. AIX

How to increase the filesystem size in HACMP

How to increase the filesystem size in HACMP. what is the difference between normal chfs command and increase the filesystem size in HACMP. (4 Replies)
Discussion started by: AIXlearner
4 Replies

7. UNIX for Dummies Questions & Answers

Increase size to sd[b-c]

hi guys I am working on my vmware workstation. I have a /dev/sdb which is 5GB. I am using LVM. Now I increase /dev/sdb 2 more GB. fdisk -l shows 7 GB but pvscan still shows 5GB. how do I make my system recognize the new 7GB added and be able to add those to my physical volumen and... (1 Reply)
Discussion started by: kopper
1 Replies

8. AIX

PowerHA HACMP on VIOS servers

Few questions regarding Power HA ( previously known as HACMP) and VIOS POWERVM IVM ( IBM Virtualization I/O Server ) Is it possible to create HACMP cluster between two VIOS servers Physical Machine_1 VIOS_SERVER_1 LPAR_1 SHARED_DISK_XX VIOS_SERVER_2 Physical Machine_2 LPAR_2... (6 Replies)
Discussion started by: filosophizer
6 Replies

9. AIX

Uniform LUN size

Hi, Is there any advantage is making all my storage LUNS ( hdisk ) of uniform size. Currently the LUN's are having different size () eg: 50G / 60G / 75G etc ). I am planning for a storage migration....so should i go for uniform lun size or with current LUN size pattern ? Regards, jibu (3 Replies)
Discussion started by: jibujacob
3 Replies

10. AIX

Increase filesystem size AIX 5.3

I an trying to increase the file size on an AIX 5.3 box. I think i am missing the correct syntax for the command. Here is was i am trying on a test box # lsvg rootvg VOLUME GROUP: rootvg VG IDENTIFIER: 0000bd8b00004c00000 0010d8ed7a76e VG STATE: active ... (3 Replies)
Discussion started by: fierfek
3 Replies
vgimport(1M)															      vgimport(1M)

NAME
vgimport - import an LVM volume group onto the system SYNOPSIS
mapfile] vg_name pv_path ... mapfile] infile] vg_name mapfile vg_name DESCRIPTION
The command adds the specified volume group to the system. The physical volumes, specified as pv_path ..., are scanned to obtain the vol- ume group information and logical volume information. This command works much like A user may explicitly create the vg_name directory and the file before importing the volume group. If absent, the command will automatically create the directory and the file, assigning the minor number as explained in the command man page (see vgcreate(1M)). The vg_name is added to the or file, and the associated logical volume device files are added to the system. assumes that the volume group information has already been created on the physical volumes. This command is useful in conjunction with the command (see vgexport(1M)), to move volume groups from one system to other systems within a high availability cluster. creates logical volume device files under the vg_name directory using the naming convention given in mapfile or using the default naming convention used by the command (see lvcreate(1M)). The command reconstructs the newly imported volume group entry in the or file. The order of the disks belonging to the newly imported vol- ume group could be different than it was before. When a bootable volume group is imported (volume groups version 1.0 only), the boot information present in the boot disks might be incor- rect due to the change in the order of disks in the file. This is because the boot information on the boot disks assumes a certain order of disks in and requires a resynchronization of this information after the first activation of a newly imported bootable volume group. To resynchronize the information on the boot disk after the first activation of a newly imported bootable volume group, run the command in recovery mode option). does not activate the imported volume group due to the many possible options at volume group activation time. To activate the volume group once it has been successfully imported, use the command (see vgchange(1M)). Options and Arguments recognizes the following options and arguments: pv_path The block device path names of a physical volume. This argument is not used with the and related options. vg_name The path name of the volume group. Specify the name of the file from which logical volume names and numbers are to be read. This option is optional when used as in the first com- mand line format of the If this option is not specified, logical volume names are created using the default naming convention where is the decimal representation of logical volume minor number. When used with the option, the volume group specified in the mapfile can be shared among the exporting system and the importing systems. Configure the volume group by populating persistent device special files in the or file, corresponding to the volume group, vg_name. (See intro(7) for information about device special files.) This option can only be used with option. If is invoked without a option, legacy device special files will be used to populate the or file. This option may become obsolete in future releases. Scan option. Scan each of the disks connected to the system and update the or file with the physical volumes that have matching volume group information, as found in the mapfile. This option should always be used in conjunction with the option. The specified mapfile is the file gener- ated by running the command, also with and options. Preview the actions to be taken but do not update the or file or add the logical volume device files. This option is best used in conjunction with the option. Print verbose messages including names of the logical volumes. Import the set of pv_paths held in the infile into the volume group. This option is used as an alternative to specifying the pv_paths on the command line. Each pv_path must appear on a new line in the infile. This option may not be used together with the option. WARNINGS
The option may become obsolete in future releases. No more than eight paths to any physical volume will be added to the or file. All other paths wll be omitted. The following warnings apply to the option, when importing disks with alternate paths: The command does not preserve the path ordering, when a volume group is exported and then imported. This may cause the primary and alter- nate paths to be different on an importing system, from that of an exported system. Also, additional alternate paths that were not config- ured on the exported system may get discovered and configured on the importing system. If the original primary path of a disk gets configured as an alternate path after the volume group is imported, the order can easily be reverted by using to remove the primary path and then reconfiguring the same path again as an alternate, using If additional alternate paths were added to the newly imported volume group, use to reduce any alternate paths that were added but not required. EXTERNAL INFLUENCES
Environment Variables determines the language in which messages are displayed. If is not specified or is null, it defaults to "C" (see lang(5)). If any internationalization variable contains an invalid setting, all internationalization variables default to "C" (see environ(5)). EXAMPLES
Import the volume group that is located on physical disks and Activate the volume group following a successful import: Import the volume group using the mapfile, was previously specified by the command on another system. The volume group, is specified in and will be used by the importing system only: Import the volume group using the mapfile, was previously specified by the command on another system. The volume group, is specified in and will be shared among the exporting system, this system, and other systems importing the volume group as shared: Import the volume group using the infile, was previously specified by the command on another system, and it assumes that pv_paths in the are identical on both systems. SEE ALSO
vgexport(1M), vgscan(1M), intro(7), lvm(7). vgimport(1M)
All times are GMT -4. The time now is 09:51 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy