Sponsored Content
Operating Systems AIX How to manually -re-attach AIX lv's to a mirror? Post 303028828 by mrmurdock on Tuesday 15th of January 2019 05:09:00 PM
Old 01-15-2019
so migratepv -l hd2 hdisk1 hdisk6 (yes I found a spare unused disk allocated, but I can delete the lv and vg on it. Smilie). My only concern would be since it cannot read the bad block to finish the mirror, is migratepv smart enough to move the stuck lv? I guess if migratepv cant, it will just error out.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Display Mirror State AIX

Hello, how can i see easily the state of a mirrored disk on a AIX 4.3.3. I try followed command: lslv -m >lvname> but for me is not enough information. thanx in advance fenomen (2 Replies)
Discussion started by: fenomen
2 Replies

2. Solaris

ZFS Mirror versus Hardware Mirror

I've looked a little but haven't found a solid answer, assuming there is one. What's better, hardware mirroring or ZFS mirroring? Common practice for us was to use the raid controllers on the Sun x86 servers. Now we've been using ZFS mirroring since U6. Any performance difference? Any other... (3 Replies)
Discussion started by: Lespaul20
3 Replies

3. Solaris

What is mirror and sub mirror in RAID -1 SVM

Hi , I am new to SVM .when i try to learn RAID 1 , first they are creating two RAID 0 strips through metainit d51 1 1 c0t0d0s2 metainit d52 1 1 c1t0d0s2 In the next step metainit d50 -m d51 d50: Mirror is setup next step is metaattach d50 d52 d50 : submirror d52 is... (7 Replies)
Discussion started by: vr_mari
7 Replies

4. AIX

AIX Rootvg mirror and sysdumplv

Guys, In my AIX 6.1 box the rootvg was on hdisk2, I tried to migrated it to hdisk0 Added hisk0 to rootvg , mirrored rootvg and changed bootlist and and sucessfully rebooted from hdisk0 Now I tried to remove the hdisk2 from rootvg so breaked mirror -bash-3.00# unmirrorvg rootvg hdisk2... (3 Replies)
Discussion started by: kkeng808
3 Replies

5. AIX

Attach HP EVA to IBM AIX powerpc singlepath

Dear all. We have a very big issue on Attach HP EVA to IBM AIX powerpc singlepath. the configurations on lscfg -vl fcs2 fcs2 U789C.001.DQD8D74-P1-C2-T1 4Gb FC PCI Express Adapter (df1000fe) Part Number.................10N7249 Serial... (3 Replies)
Discussion started by: Juri_al
3 Replies

6. AIX

Clone or mirror your AIX OS larger disk to smaller disk ?

hello folks, I have a 300GB ROOTVG volume groups with one filesystem /backup having 200GB allocated space Now, I cannot alt disk clone or mirrorvg this hdisk with another smaller disk. The disk size has to be 300GB; I tried alt disk clone and mirrorvg , it doesn't work. you cannot copy LVs as... (9 Replies)
Discussion started by: filosophizer
9 Replies

7. 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

8. AIX

AIX break rootvg mirror from system down

Hello, aix 5.2, mirrored rootvg on hdisk0 and hdisk1. hdisk0 is dead. I can boot to cd, into sms, into maintenance mode. I can fsck all the various partitions on hdisk1 (the hd4 hd2 hd3, etc...) all is fine. But without the hdisk0 part of the mirror I cannot get the system to boot. ystem hangs on... (6 Replies)
Discussion started by: sshapiro
6 Replies

9. AIX

AIX hdisk Mirror vs alt_clone

Hello, I have two hdisk in Power7 machine, the rootvg on hdisk0. So to make a disk redundancy should make mirror or alt_clone and what is the different. Appreciate your help Thanks (1 Reply)
Discussion started by: moudmm
1 Replies

10. UNIX for Beginners Questions & Answers

AIX - mirror a jfs2log

Hi everybody, I have a little problem with my AIX 6.1, PowerHA 6.1 LVM mirroring. I accidentally created logical volume cpsabcd2lv with external jfs2log loglv00 in the same volume group cpsdata2vg. Then I mirrored LV cpsabcd2lv on the second LUN in VG cpsdata2vg. My journal is unmirrored and... (0 Replies)
Discussion started by: Necronomic
0 Replies
lvdisplay(1M)															     lvdisplay(1M)

NAME
lvdisplay - display information about LVM logical volumes SYNOPSIS
lv_path ... Remarks If the logical volume input arguments belong to a combination of volume groups versions 1.0 and 2.0 or higher, the arguments may not be processed in the order they are listed on the command line. Mirrored disk information requires the installation of the optional HP MirrorDisk/UX software, which is not included in the standard HP-UX operating system. DESCRIPTION
The command displays the characteristics and status of each logical volume specified by lv_path. Options and Arguments recognizes the following options and arguments: lv_path The block device path name of a logical volume, for example, Produce a compact listing of fields described in The output is a list of colon separated fields formatted as value...]. For each logical volume, display the physical volume distribution, and the mapping of the logical extents onto the physical extents of the physical volumes. This option displays the same information as the option, except in the column where is displayed, the (Physical Volume Number in VG) will be displayed instead. Use this option with the option. Display Without -v Option If you omit the option, displays the following information for each logical volume: The block device path name of the logical volume. The path name of the volume group. The access permission and quiesce mode: The access permission is either: or If the VG containing the LV is quiesced, the quiesce mode is displayed on the same line. The quiesce mode is either: or State of the logical volume: Available but contains physical extents that are not current. Available with no stale extents. Not available for use. Number of mirror copies. Mode of mirror consistency recovery which determines how LVM performs mirror consistency recovery during volume group activation: Recover mirror consistency by using the Mirror Write Cache and Mirror Consistency Record. Implies that Mirror Write Cache is on. Recover mirror consistency by going through all logical extents and copying data from a non-stale copy to the other mirror copies. Implies that Mirror Write Cache is off. No mirror consistency recovery during volume group activation on this logical volume following a system crash. The user of the logical volume is responsible for ensuring mirror consistency. Implies that Mirror Write Cache is off. Striped, sequential or parallel scheduling policy. Striped policy is by default parallel scheduling for mirrored I/O. Size of the logical volume in megabytes (MB). Number of logical extents currently in the logical volume. Number of physical extents allocated to the logical volume. The number of stripes. If this field is 0, then the logical volume is not striped. The size of each stripe in kilobytes (KB). Bad block relocation policy. Current allocation state, displayed as one of: Physical extents are allocated in an ascending order without any gap between adjacent extents. All physical extents of a given mirror are contained in a single physical volume. Distributed allocation is turned on and any two consecutive logical extents are guaranteed to be located on different physical volumes. See lvcreate(1M) for more information. Distributed allocation is turned on but any two consecutive logical extents are NOT guaranteed to be located on different physical volumes. See lvchange(1M) for more information. Physical extents that belong to the same logical extent can be allocated on the same physical volume or physical volume group. Mirror copies for a logical extent are not allocated on the same physical volume group. Mirror copies for a logical extent are not allocated on the same physical volume. The IO timeout used by LVM for all IO to this logical volume. A value of default, indicates that the system will use the value of "forever". (Note: the actual duration of a request may exceed this timeout value when the underlying physical volume(s) have timeouts which either exceed this value or are not integer multiples thereof.) Display With -v Option If you specify the option, also lists the distribution of each logical volume across the physical volumes of the volume group and the map- ping of each logical extent of the logical volume on the physical extents of the physical volume. The distribution of logical volume lv_path across the physical volumes of the volume group, displayed in the following columns: The block device path name of the physical volume where the logical extents are allocated. The Physical Volume Number in VG (if option is specified). Number of logical extents allocated on the physical volume. Number of physical extents allocated on the physical volume. The mapping of logical extents onto physical extents, displayed in the following columns: Logical extent number. The block device path name of the physical volume that corresponds to the location of the first physical extent of the logical extent. First physical extent number allocated to the logical extent. Status of the first physical extent: or The following columns are displayed if there is at least one mirror copy: The block device path name of the physical volume that corresponds to the location of the second physical extent (first copy) of the logical extent. Second physical extent number allocated to the logical extent. Status of the second physical extent: or The following columns are displayed if there are at least two mirror copies: The block device path name of the physical volume that corresponds to the location of the third physical extent (second copy) of the logical extent. Third physical extent number allocated to the logical extent. Status of the third physical extent: or If there are more than 3 physical extents associated with one logical extent (applicable for logical volumes created within volume groups versions 2.0 or higher only), then a second line of physical extent(s) is displayed for the logical extent. The rest of the line contains the following columns: The following columns are displayed if there are at least three mirror copies: Logical extent number. The block device path name of the physical volume that corresponds to the location of the fourth physical extent(third copy) of the logical extent. Fourth physical extent number allocated to the logical extent. Status of the fourth physical extent: or The following columns are displayed if there are at least four mirror copies: The block device path name of the physical volume that corresponds to the location of the fifth physical extent (fourth copy) of the logical extent. Fifth physical extent number allocated to the logical extent. Status of the fifth physical extent: or The following columns are displayed if there are five mirror copies: The block device path name of the physical volume that corresponds to the location of the sixth physical extent(fifth copy)of the logical extent. Sixth physical extent number allocated to the logical extent. Status of the sixth physical extent: or Compact Listing (-F Option) The option generates a compact and parsable listing of the command output in colon separated fields formatted as value...]. The option is designed to be used by scripts. The resulting command output may be split across multiple lines. The output may include new keys and/or values in the future. If a key is deprecated, its associated value is set to For the current version of the command, the lines format is: The format of Line 1 is as follows: lv_name=value:vg_name=value:lv_permission=value:lv_status=value: mirror_copies=value:consistency_recovery=value:schedule=value: lv_size=value:current_le=value:allocated_pe=value:stripes=value: stripe_size=value:bad_block=value:allocation=value:used_pv=value: io_timeout=value The format of Line 2 is as follows: pv_name=value:le_on_pv=value:pe_on_pv=value The above line may be repeated with different values. The format of Line n is as follows: le=value:pv1=value:pe1=value:status_1=value[:...:pvN=value:peN=value: status_N=value] The above line may be repeated with different values. 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
Display information about a logical volume: Display all the available information about a logical volume, including the characteristics, status and distribution map: Display all the available information about a logical volume, but display instead of in the status and distribution map. SEE ALSO
lvchange(1M), lvcreate(1M), lvextend(1M), lvmadm(1M), lvreduce(1M), lvm(7), pvdisplay(1M), vgdisplay(1M). lvdisplay(1M)
All times are GMT -4. The time now is 08:41 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy