Sponsored Content
Full Discussion: How to extend mirrored VG?
Operating Systems AIX How to extend mirrored VG? Post 302682937 by unclefab on Tuesday 7th of August 2012 04:26:04 AM
Old 08-07-2012
The problem here is I would need to keep a minimum of control of this mirroring on my VG, means new disk1 mirrored to new disk2.
 

10 More Discussions You Might Find Interesting

1. HP-UX

Number of Disk Mirrored in HP-UX

In HP-UX 11.00 How can i check if there are disks mirrored (2 Replies)
Discussion started by: cgege
2 Replies

2. AIX

Mirrored disk.....

How do I know, which all disks are mirrored? any command? Bala (7 Replies)
Discussion started by: balaji_prk
7 Replies

3. AIX

How to list mirrored elements? (pv, vg, lv)

Hello, How can I list mirrored elements, such as PV, VG or LV? (and others if applicable). On AIX 4.3.3 and 5.3.0. I tried the commands: lscfg|grep hd lspv lsvg lsvg -l (of each vg) lslv (and some options) But could not find what am I looking for. I saw a "number of copies", but I am... (4 Replies)
Discussion started by: cactux
4 Replies

4. HP-UX

MirrorDisk UX: Should DUMP Be Mirrored?

Follwing up on what I was working on yesterday, I noticed that at this thread, someone was suggesting that you WOULDN'T want to mirror DUMP. When I boot with my current secondary disk (because I didn't mirror DUMP) I get an error indicating that DUMP isn't there. Why wouldn't I want to mirror... (1 Reply)
Discussion started by: deckard
1 Replies

5. Solaris

Backup for HW Mirrored Disks

We use SW mirroring (RAID1) using SVM for our SUN servers (which we OEM to end clients with our application on). When I need to make a tape backup for the server (disk), I disable mirroring and perform backup of the entire disk to tape using ufsdump. This process requires an outage and sensitive as... (8 Replies)
Discussion started by: StarSol
8 Replies

6. AIX

Identify mirrored Pv in aix

Guys.. Any one can help me to how to identify primary mirrored disk in mirrored VG in aix 5.3.. (5 Replies)
Discussion started by: sumathi.k
5 Replies

7. Solaris

Are my disks mirrored ?

# metastat d1: Mirror Submirror 0: d11 State: Okay Submirror 1: d12 State: Okay Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Size: 14582208 blocks (7.0 GB) d11: Submirror of d1 State: Okay Size: 14582208 blocks... (2 Replies)
Discussion started by: Exposure
2 Replies

8. Solaris

Boot from Mirrored disk

So I have mirrored disk already set up from c1t0d0 to c1t1d0. Is there some special procedures that I need to do before I do and then try to boot from the mirrored disk? I am using a V490 if that helps... (7 Replies)
Discussion started by: drew_1980
7 Replies

9. AIX

rootvg mirrored

I want to increase the size of /tmp by 1GB I know that the command is chfs -a size=+1G /tmp But the rootvg is mirrored and when I do a lsvg -p rootvg, I could see 2 disks. Will there be any impact if I increase the size of /tmp when the rootvg is mirrored ? Please advise. (1 Reply)
Discussion started by: newtoaixos
1 Replies

10. HP-UX

[Solved] How to extend a mirrored logical volume?

Want to extend the /home filesystem: Filesystem kbytes used avail %used Mounted on /dev/vg00/lvol4 262144 260088 2056 99% /home root@server:./root # vgdisplay vg00 --- Volume groups --- VG Name /dev/vg00 VG Write Access read/write VG Status available Max LV 255 Cur LV 11 Open... (4 Replies)
Discussion started by: proactiveaditya
4 Replies
lvextend(1M)															      lvextend(1M)

NAME
lvextend - increase space, increase mirrors for LVM logical volume SYNOPSIS
autobackup] le_number | lv_size | mirror_copies lv_path [pv_path ... | pvg_name ...] Remarks Mirrored disk operations require the installation of the optional HP MirrorDisk/UX software, which is not included in the standard HP-UX operating system. DESCRIPTION
The command can increase a logical volume's allocated extents, or increase its number of mirrored copies. Other logical volume characteristics can be modified with the and commands (see lvchange(1M) and lvreduce(1M)). To limit the allocation to specific physical volumes, specify the physical volume names as pv_path arguments or specify the physical volume group names as pvg_name arguments. Otherwise, all of the physical volumes in a volume group are available for allocating new physical extents. LVM always ensures that physical extent allocation can satisfy the current allocation policy or policies. If a physical volume is not suitable for use with a certain allocation policy, it is not used during physical extent allocation, even it is specified in a pv_path argument or indirectly in a pvg_name argument. The pvg_name argument is allowed only if one of the allocation policies of the logical volume is PVG-strict. Options and Arguments The option is only meaningful if the optional HP MirrorDisk/UX software has been installed. recognizes the following options and arguments: lv_path The block device path name of a logical volume. pv_path The block device path name of a physical volume. pvg_name The name of a physical volume group (see lvmpvg(4)). 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 logical volume. This is the default. After this command executes, the command (see vgcfgbackup(1M)) is executed for the volume group to which the logical volume belongs. Do not back up configuration changes this time. Increase the space allocated to the logical volume, specified in logical extents. le_number is a decimal value greater than the current number of logical extents. le_number must be at least 1 and no greater than a volume group version-dependent maximum; use the command to determine the maximum number of logical extents for the volume group version. One, and only one, or option must be supplied. Increase the space allocated to the logical volume, specified in megabytes. lv_size is a decimal value greater than the current logical volume size. lv_size must be at least 1 and no greater than a volume group version-dependent maximum; use the command to determine the maximum logical volume size for the volume group version. lv_size is rounded up to the nearest multiple of the logical extent size, equivalent to the physical extent size defined for the volume group by the command (see vgcreate(1M)). One, and only one, or option must be specified. Set the number of mirror copies allocated for each logical extent. A mirror copy contains the same data as the original. mirror_copies must be at least 1 and no greater than a volume group version-dependent maximum; use the command to determine the maximum number of mirror copies for the volume group version. mirror_copies must be greater than the current value. Data in the new copies is synchronized unless the option is specified. The synchronization process can be time consuming, depending on hardware characteristics and the amount of data. One, and only one, or option must be specified. Do not synchronize the new mirror copies. This may affect data high availability so use or to synchronize the mirrors. The option must be specified along with this option. Striped Logical Volume considerations Striped and mirrored logical volumes are supported. An increase in size of a striped logical volume is done by increments of stripes logical extents. One increment corresponds to stripes physical extents if the volume is not mirrored or to stripes * (mirror_copies + 1) physical extents if the volume is mirrored. stripes is the number of disks the logical volume is striped across. It is set with the option stripes of the command. mirror_copies is the number of mirror copies allocated for each extent. It is set with the option of the and commands. LVM striped logical volumes are always allocated using the strict or PVG-strict allocation policies. Each physical extent of an increment is allocated on a different physical volume in the volume group. A size increase of a striped volume requires at least stripes (or stripes * (mirror_copies + 1) if the volume is mirrored) physical volumes with adequate free space and meeting the allocation policy. An increase of the number of mirror copies of a striped volume requires at least (stripes times the number of copies to add) physical vol- umes with adequate free space and meeting the allocation policy. 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). If physical volume groups are passed as arguments, uses the physical volume group file of the system where the command is issued (the server). 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
Increase the number of the logical extents of a logical volume to 100: Increase the logical volume size to 400 MB: Allocate two mirrors (that is, two copies of the original) for each logical extent of a logical volume: Mirror a logical volume onto a particular physical volume. Allocate one mirror and do not synchronize the new mirror copy: Increase the size of a file system existing on a logical volume. First, increase the size of the logical volume. Unmount the file system. Extend the file system to occupy the entire (larger) logical volume. Remount the file system. WARNINGS
The creation of striped and mirrored logical volume(s) may prevent the import and activation of the volume group on an earlier HP-UX release. See lvcreate(1M) on the earlier release to see if it explicitly states that striping and mirroring is supported. If the striped and mirrored logical volumes of the volume group are removed or un-mirrored, the volume group becomes again compatible with the older HP-UX releases. SEE ALSO
lvchange(1M), lvcreate(1M), lvdisplay(1M), lvmadm(1M), lvmpud(1M), lvreduce(1M), lvsync(1M), pvchange(1M), pvdisplay(1M), vgsync(1M), intro(7), lvm(7). lvextend(1M)
All times are GMT -4. The time now is 03:46 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy