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

NAME
volrecover - Performs volume recovery operations SYNOPSIS
/sbin/volrecover [-g diskgroup] [-sb] [-o options] [volume | medianame...] OPTIONS
Options that can be specified to volrecover are: Starts disabled volumes that are selected by the operation. Volumes will be started before any other recovery actions are taken. Volumes will be started with the -o delayrecover start option. This requests that any opera- tions that can be delayed in starting a volume will be delayed. In other words, only those operations necessary to make a volume available for use will occur. Other operations, such as mirror resynchronization, attaching of stale plexes and subdisks, and recovery of stale RAID5 parity will normally be delayed. Performs recovery operations in the background. With this option, volrecover will put itself in the back- ground to attach stale plexes and subdisks, and to resynchronize mirrored volumes and RAID5 parity. If this is used with -s, volumes will be started before recovery begins in the background. Performs no recovery operations. If used with -s, volumes will be started, but no other actions will be taken. If used with -p, the only action of volrecover will be to print a list of startable volumes. Prints the list of selected volumes that are startable. For each startable volume, a line is printed containing the following information: the volume name, the disk group ID of the volume, the volume's usage type, and a list of state flags pertaining to mirrors of the volume. State flags and their meanings are: One of the mirrors was detached by an I/O failure One of the mirrors needs recovery, but the recovery is related to an administrative operation, not an I/O failure Neither kdetach nor stale is appropriate for the volume. Displays information about each task started by volrecover. For recovery operations (as opposed to start operations), a completion status is printed when each task completes. Displays commands that volrecover would execute without actually executing them. Lim- its operation of the command to the given disk group, as specified by disk group ID or disk group name. If no volume or medianame operands are given, all disks in this disk group will be recovered; otherwise, the volume and medianame operands will be evaluated relative to the given disk group. Without the -g option, if no operands are given, all volumes in all imported disk groups will be recovered; otherwise, the disk group for each medianame operand will be determined based on name uniqueness within all disk groups. Passes the given option argu- ments to the -o options for the volplex att and volume start operations generated by volrecover. An option argument of the form pre- fix:options can be specified to restrict the set of commands that the -o option should be applied to. Defined prefixes are: Applies to all invocations of the volume utility (volume starts, mirror resynchronizations, RAID5 partity rebuilds, and RAID5 subdisk recoveries) Applies to all invocations of the volplex utility (currently used only for attaching plexes) Applies specifically to plex attach operations applies specifically to volume start operations Applies to subdisk recoveries Applies to mirror resynchronization and RAID5 parity recovery DESCRIPTION
The volrecover program performs plex attach, RAID5 subdisk recovery, and resynchronize operations for the named volumes, or for volumes residing on the named disks (medianame). If no medianame or volume operands are specified, the operation applies to all volumes (or to all volumes in the specified disk group). If -s is specified, disabled volumes will be started. With -s and -n, volumes are started, but no other recovery takes place. Recovery operations will be started in an order that prevents two concurrent operations from involving the same disk. Operations that involve unrelated disks will run in parallel. EXAMPLES
To recover, in the background, any detached subdisks or plexes that resulted from replacement of a specified disk, use the command: # volrecover -b medianame If you want to monitor the operations, use the command: # volrecover -v medianame SEE ALSO
volintro(8), volplex(8), volume(8) volrecover(8)
All times are GMT -4. The time now is 06:13 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy