Sponsored Content
Operating Systems AIX Clone or mirror your AIX OS larger disk to smaller disk ? Post 302766623 by filosophizer on Tuesday 5th of February 2013 05:25:21 AM
Old 02-05-2013
How to make free PP in Volume group

Okay,

I have a 10GB hdisk with AIX 5.3 with 0 free PPs, and I assigned a 15GB hdisk
made a successful alt_disk_clone on the new empty disk , however the new cloned disk should have free PPs but as it is cloned there is no free PPs.

Is there any way to allocate free PPs for the volume group of the cloned disk ?

Thanks
 

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
voldiskadd(8)						      System Manager's Manual						     voldiskadd(8)

NAME
voldiskadd - Adds one or more disks for use with the Logical Storage Manager SYNOPSIS
/usr/sbin/voldiskadd disk-address-list DESCRIPTION
The voldiskadd utility sets up new disks that are added to the system after the initial system installation and configures the disks for use by the Logical Storage Manager. A valid disk label must exist on the disk before using the voldiskadd utility. One or more disks may be specified using a disk-address-list. Disk addresses in the list have the form dskn (for the entire disk) or dsknp (for a specific partition). When specifying multiple disks, use a space between entries. Disk address names relate directly to device names in the /dev/disk directory. For example, here are some valid voldiskadd disk-address-list specifications: # voldiskadd dsk1 # voldiskadd dsk2 dsk3a The file, /etc/vol/disks.exclude, may be used to exclude disks from use by voldiskadd. Each line of the file specifies the name of a disk to exclude (for example, dsk5). The voldiskadd utility prompts the user for a disk group name and disk media name for the disks. If a new disk group name is specified, that disk group is created for the new disks. If no disk group name is specified, the disks are left as unassigned replacement disks for future use. If an existing disk group name is specified, the user is prompted for whether the disks should be designated as spares for the disk group. If a disk is found to already contain non-Logical Storage Manager partitioning, the user is asked whether the disk should be encapsulated. Encapsulation turns each partition of the disk into a volume. A disk should be encapsulated if it contains file systems or data that should not be overwritten. If encapsulation is not desired for a disk, the disk can be initialized as a new disk for use by the Logical Storage Manager. For new disks, all space on the disk becomes free space in the disk's disk group. Context-sensitive help is available at every prompt by typing ?. Also, a list option can be used to get information on available target disks for an operation. The voldiskadd utility supports the following general classes of actions: Initializing a disk with reserved regions and partitions. Disk initialization is performed by calling voldisksetup command. Adding a disk to an existing disk group. This operation can be performed independently of the initialization of the disk drive to add a disk's storage space to a disk group's free space pool. The volassist command may subsequently allocate from that free space. The disk can also be added as a hot spare device. Creating new disk groups in which to import new disks. If no disk group exists for importing disks, the option of creating the disk group is offered. Encapsulating disks that have exist- ing contents. This is the default action for disks that do not have a valid, existing Logical Storage Manager private region, but that do have a disk label. Encapsulation is performed by calling volencap. Reconnecting a drive that was temporarily inaccessible. This situation is detected automatically, by noting that the specified drive has a disk ID that matches a disk media record with no currently associated physical disk. After reconnection, any stale plexes referring the disk are reattached, and any stopped volumes referring the disk are restarted. This reattach action is performed by calling the volrecover script. ERRORS
You may receive the following messages when using the voldiskadd command: Initialization of disk device special-device failed. Error: special-device or an overlapping partition is open. This message indicates that the partition you specified or an overlapping partition on the disk is actively in use. The partition could be a mounted UFS or AdvFS filesystem, initialized as an LSM disk or used as a swap device. special-device is marked in use for fstype in the disklabel. If you continue with the operation you can possibly destroy existing data. Would you like to continue?? [y,n,q,?] (default: n) This message indicates that the fstype of a partition or an overlapping partition is set in the disk label. The voldiskadd command prints this message to warn that a disk partition may have valid data which could be destroyed. If you are sure that the disk partition does not have valid data and that the partition can be added to LSM, you can ignore the warning message by entering y at the prompt. The voldiskadd command will proceed to initialize the disk partition and add it to LSM. FILES
A list of disks to exclude from use by voldiskadd. SEE ALSO
disklabel(8), volassist(8), voldisk(8), voldiskadm(8), voldisksetup(8), voldg(8), volintro(8) voldiskadd(8)
All times are GMT -4. The time now is 10:46 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy