Sponsored Content
Full Discussion: AIX - stale partition
Operating Systems AIX AIX - stale partition Post 303038496 by rbatte1 on Wednesday 4th of September 2019 01:00:32 PM
Old 09-04-2019
My apologies for being away for a few days. There should be no difference with the process because they will both do the same thing. If the lost LUN is now available and visible to the volume group, then the sync, however it runs will have to read the appropriate physical partitions from the good side and copy them to the stale side if the PP has been updated. It will not copy the data if the PP has not updated, but for a large LV, this process can take some time to complete.

You should be able to monitor it from another session so you get an idea of progress and see the stale PP count reducing.




Robin
This User Gave Thanks to rbatte1 For This Post:
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Unix Stale Mounts

Is there an easy way to find all stale mounts on a system? (2 Replies)
Discussion started by: derf912
2 Replies

2. UNIX for Dummies Questions & Answers

I've created a partition with GNU Parted, how do I mount the partition?

I've created a partition with GNU Parted, how do I mount the partition? The manual information at http://www.gnu.org/software/parted/manual/parted.html is good, but I am sure about how I mount the partition afterwards. Thanks, --Todd (1 Reply)
Discussion started by: jtp51
1 Replies

3. UNIX for Dummies Questions & Answers

removing stale partitions

hi, i was trying to mirror root volume group and the command i was using didnt respond for a long time mirrorvg -m rootvg hdisk1 I was checking rootvg and it gives below. how do i fix stale partitions?? it seems to be on hdisk1 LV NAME TYPE LPs PPs PVs LV STATE ... (2 Replies)
Discussion started by: karthikosu
2 Replies

4. HP-UX

Stale users and no process

HP-UX B.11.23 U ia64 I've got two users that show in "w" with long idle times but if I search for their processes I find nothing (ps -ef | grep username ) I'm not sure why "w" still sees them and if there is anything (short of a reboot) that I can do to clean them out. Ideas? (8 Replies)
Discussion started by: LisaS
8 Replies

5. Solaris

Partition overlaps another partition while creating new parition in solaris

hi all while formatting hard disk i am getting following error. Partition 1 ends at 266338338 It must be between 34 and 143374704. label error: EFI Labels do not support overlapping partitions Partition 8 overlaps partition 1. Warning: error writing EFI. Label failed. I have formatted the... (2 Replies)
Discussion started by: nikhil kasar
2 Replies

6. AIX

AIX 5.3 using raw partition for Oracle 10g

Hellow friends, We are having AIX 5.3 total memory allotted to /Backup directory is 700GB actual used memory is 250GB ..but when i issue df -gt command to check space it is showing /Backup directory is 70% full ..how to identify root cause.? (1 Reply)
Discussion started by: umashankar1987
1 Replies

7. HP-UX

Bypass stale PE ?

Hello, I have an ancient HP-UX 11.11 system where I have a logical volume marked stale and I can't get it sync'd. I have tried lvsync and lvreduce/lvextend to no avail. It is just one 4Mb PE on the disk that I can't get current. # lvdisplay -v /dev/vg00/lvol5 | grep stale LV Status ... (17 Replies)
Discussion started by: port43
17 Replies

8. AIX

Hd6 is in stale condition

Hi friends, the paging lv hd6 is in stale condition hd6 paging 48 96 2 open/stale N/A And i'am getting the following alerts in the server 333BD283 0811044814 U S LVDD Bad block detected with no relocation al 333BD283 0811041114 U S LVDD ... (1 Reply)
Discussion started by: Mohamed Thamim
1 Replies

9. Red Hat

Shrink LVM partition & create new Linux Primary partition

Hello All, I have a Red Hat Linux 5.9 Server installed with one hard disk & 2 Partitions created on it as follows, /boot - Linux Partition & another is LVM - One VG & under that 5-6 Logical volumes(var,opt,home etc). Here my requirement is to take out 1GB of space from LVM ( Any logical... (5 Replies)
Discussion started by: gr8_usk
5 Replies

10. AIX

Stale PPs in AIX, failed disks.. how to replace?

I have a AIX 7.1 system that has 3 failed disks, 1 in rootvg and 2 in vg_usr1. Here is the output of lspv. # lspv hdisk0 00044d4dfbb11575 vg_usr1 active hdisk1 0000150179158027 vg_usr1 active hdisk2 ... (11 Replies)
Discussion started by: c3rb3rus
11 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:35 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy