Sponsored Content
Operating Systems AIX Clone or mirror your AIX OS larger disk to smaller disk ? Post 302768483 by filosophizer on Friday 8th of February 2013 04:09:48 PM
Old 02-08-2013
Code:
root@test1:/>lsvg rootvg

VOLUME GROUP:       rootvg                   VG IDENTIFIER:  00c7780e00004c000000013b4d2a9ce3
VG STATE:           active                   PP SIZE:        512 megabyte(s)
VG PERMISSION:      read/write               TOTAL PPs:      19 (9728 megabytes)
MAX LVs:            256                      FREE PPs:       0 (0 megabytes)
LVs:                10                       USED PPs:       19 (9728 megabytes)
OPEN LVs:           9                        QUORUM:         1
TOTAL PVs:          1                        VG DESCRIPTORS: 2
STALE PVs:          0                        STALE PPs:      0
ACTIVE PVs:         1                        AUTO ON:        yes
MAX PPs per VG:     32512                                    0
MAX PPs per PV:     1016                     MAX PVs:        32
LTG size (Dynamic): 256 kilobyte(s)          AUTO SYNC:      no
HOT SPARE:          no                       BB POLICY:      relocatable

will running this command help

Code:
 chvg -t 2 rootvg
0516-1193 chvg: WARNING, once this operation is completed, volume group rootvg
        cannot be imported into AIX 430 or lower versions. Continue (y/n) ?
y
0516-1164 chvg: Volume group rootvg changed.  With given characteristics rootvg
        can include upto 16 physical volumes with 2032 physical partitions each.

VOLUME GROUP in AIX - web-manual


I made a clone from a 10GB rootvg on 15GB rootvg , should I get the 5GB as free space -- which I am not getting it !
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Upgrade Hard Disk to a larger one

Hello folks, I have a sun sparcstation 20, I would like to upgrade one of the hard disks to a larger one. The one I would like to upgrade only contains user data. Here are my thoughts: 1. Backup the specific file system 2. Replace the disk with the larger disk 3. Create a new file... (2 Replies)
Discussion started by: DLongan
2 Replies

2. UNIX Desktop Questions & Answers

How do I clone Solaris 7 disk

could anyone give me a general idea of how i may clone a 2 Gig disk running Solaris 7 on it to another disk of the same size? currently, this system only has one disk in it though. i do have the ability to hook up another disk via SCSI. i have been told i need to boot to "miniroot" to run... (9 Replies)
Discussion started by: obosha
9 Replies

3. Solaris

Upgrading To Larger Disk?

I have just been assigned the task of upgrading to a larger disk on a e250; however, I am use to working on Linux and x86 hardware. I would be very appreciative if someone could inform me on how this procedure can be done safely. To begin with, the e250 has a 18 Gig primary scsi disk and a 18... (3 Replies)
Discussion started by: cstovall
3 Replies

4. Filesystems, Disks and Memory

clone disk

Disk cloning I had an external SCSI master disk that I used to clone to an identical external SCSI disk because the other SCSI disk would become corrupted. My original Master became corrupted so I used one of the other to good disk to copy back to the master. Unfortunately the new master needs... (1 Reply)
Discussion started by: stamperr
1 Replies

5. Solaris

disk 2 disk mirror

Dear friends & gurus i have some servers running solaris 10 intel machines,they are in mirror disk 2 disk there is no any hardware RAID only software RAID and they are in remote place. 1) solaris 10 OS c0t0d0(Disk1) & cotod1(Disk2) in mirror (SVM) 2) i want to break the mirror 3) boot... (0 Replies)
Discussion started by: niru
0 Replies

6. HP-UX

What is the difference between DRD and Root Mirror Disk using LVM mirror ?

what is the difference between DRD and Root Mirror Disk using LVM mirror ? (3 Replies)
Discussion started by: maxim42
3 Replies

7. UNIX for Advanced & Expert Users

Faster dd for disk clone

Guys can anyone tell how can we do faster disk cloning Below i found in google 1. dd if=/dev/sda of=/dev/sdb bs=4096 conv=noerror,sync So adding "conv=noerror,sync " makes it faster looks against not adding it 2. Enable write cache activated (hdparm -W1 /dev/sda) then run dd .. ... (2 Replies)
Discussion started by: heman96
2 Replies

8. Solaris

Use 'dd' to copy boot disk to larger target disk

Hi, I'm looking to copy a boot disk on an old Solaris 8 system using dd. I'll bring the system down to single user mode and begin from there. I'm copying my source disk to a larger target disk. Do I need to do anything other than the 'dd' command below because the target disk is bigger? ... (2 Replies)
Discussion started by: sparcman
2 Replies

9. AIX

Clone 1 Hard disk fromIBM Intellipoint server with AIX 5.x

Hello to all, Im having a new task in a new world (AIX - IBM Servers) I have an IBM Server (Type - 9111-285 very old one) with one Hard disk (73 GB 10 K) with AIX 5.x, and I need to clone the existing disk to another with the same specifications. Could you please give me some advice in order... (7 Replies)
Discussion started by: trevian3969
7 Replies
vgreduce(1M)															      vgreduce(1M)

NAME
vgreduce - remove physical volumes from an LVM volume group SYNOPSIS
autobackup] vg_name pv_path ... autobackup] vg_name pv_path autobackup] vg_name DESCRIPTION
The command removes each physical volume specified by a pv_path argument from volume group vg_name. The command with option removes all missing physical volumes from the volume group. All but one physical volume can be removed. The last physical volume must remain in the volume group so that the logical volume driver can continue to operate. The last physical volume in the volume group can be removed with the command (see vgremove(1M)). Before executing remove all logical volumes residing on each physical volume represented by a pv_path by executing the command (see lvre- move(1M)). Any physical volume in the pv_path list that is also a member of a physical volume group (as defined in is also removed from the physical volume group. If the physical volume happens to be the last one in the physical volume group, the physical volume group is also removed from the volume group. When a physical volume in the pv_path list has multiple the physical volume is not removed from the volume group until all the links to the volume are removed. When a physical volume in the pv_path list is the (in use) to a physical volume, removing the link forces LVM to switch to the (For information on alternate links, see lvm(7)). When the pv_path removed is an to the device, only the link is removed; the volume group and physical volume are otherwise unchanged. When a physical volume is added into volume groups version 2.0 or higher, the number of physical extents available on this device will be added into of the volume group (see vgdisplay(1M)). If the size of physical volume is such that would exceed the VG Max Extents of the volume group, the number of physical extents available on this device will be reduced accordingly (see vgextend(1M)). If a subsequent on a different physical volume, frees up space, then the number of extents allocated to the partial physical volume is automatically increased. Under these circumstances the command will display the old and the new values for the count for this partial physical volume (see pvdis- play(1M)). Options and Arguments recognizes the following options and arguments: Set automatic backup for this invocation of this command. autobackup can have one of the following values: Automatically back up configuration changes made to the volume group. This is the default. After this command executes, the command (see vgcfgbackup(1M)) is executed for the volume group. Do not back up configuration changes this time. Force the reduction of missing physical volumes from the specified volume group. obtains the name of each physical volume (PV) belonging to the volume group. It then reads the kernel PV structures to work out which PVs are missing. PVs which are missing will be candidates for removal. If all the physical extents on the missing PV are free then it will be removed from the volume group. Otherwise will report the physical to logical extent mapping. For missing PVs which have extents in use, you must free up all the extents by using the or commands (see lvreduce(1M) and lvremove(1M)) and re-run with the option. This option is most commonly used when the command (see vgdisplay(1M)) shows "Cur PV" higher than "Act PV" and all of the PVs belonging to the volume group are attached. This option only works on PVs and not on links. See the option for details on handling missing links. Removes the specified pv_path/s from the or file. This task will only be performed if the pv_path is currently marked as missing from the volume group. This option was mainly designed for the problem where the or the command place too many links beyond the max limit allowed in the or file. Currently the max limit is 8 paths to a PV (seven alternates and one primary). In this situation, invoking the command without the option will not resolve the condition because the path is not attached to the volume group. Similarly, this condition can not be overcome by invoking with the option, as the same works on physical volumes rather than the links. pv_path The block device path name of a physical volume. vg_name The path name of the volume group. Shared Volume Group Considerations For volume group version 1.0 and 2.0, cannot be used if the volume group is activated in shared mode. For volume groups version 2.1 (or higher), can be performed when activated in either shared, exclusive, or standalone mode. Note that the daemon must be running on all the nodes sharing a volume group activated in shared mode. See lvmpud(1M). In the case a PV alternate link is reduced, is updated only on the server node. In the case a PV is reduced, all the PV device special files are removed from on all the nodes sharing the volume group. When a node wants to share the volume group, the user must first execute a if physical volumes were removed at the time the volume group was not activated on that node. LVM shared mode is currently only available in Serviceguard clusters. 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
Remove physical volume from volume group Force, reduction of missing PVs from volume group: The following messages will appear after missing PVs has been removed successfully: PV with key 0 successfully deleted from vg Repair done, please do the following steps.....: 1. Save or to another file. 2. Remove or 3. Use to recreate or 4. NOW use to save the LVM setup. Remove the physical volume from the volume group when the physical volume is still in the or file but is currently marked as missing from the volume group: SEE ALSO
lvmpud(1M), vgchange(1M), vgcreate(1M), vgdisplay(1M), vgextend(1M), intro(7), lvm(7). vgreduce(1M)
All times are GMT -4. The time now is 01:42 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy