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
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?
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
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
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
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
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
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
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
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
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
LEARN ABOUT NETBSD
pvmove
PVMOVE(8) System Manager's Manual PVMOVE(8)
NAME
pvmove - move physical extents
SYNOPSIS
pvmove [--abort] [--alloc AllocationPolicy] [-b|--background] [-d|--debug] [-h|--help] [-i|--interval Seconds] [-v|--verbose] [-n|--name
LogicalVolume] [SourcePhysicalVolume[:PE[-PE]...] [DestinationPhysicalVolume[:PE[-PE]...]...]]
DESCRIPTION
pvmove allows you to move the allocated physical extents (PEs) on SourcePhysicalVolume to one or more other physical volumes (PVs). You
can optionally specify a source LogicalVolume in which case only extents used by that LV will be moved to free (or specified) extents on
DestinationPhysicalVolume(s). If no DestinationPhysicalVolume is specified, the normal allocation rules for the volume group are used.
If pvmove gets interrupted for any reason (e.g. the machine crashes) then run pvmove again without any PhysicalVolume arguments to restart
any moves that were in progress from the last checkpoint. Alternatively use pvmove --abort at any time to abort them at the last check-
point.
You can run more than one pvmove at once provided they are moving data off different SourcePhysicalVolumes, but additional pvmoves will
ignore any logical volumes already in the process of being changed, so some data might not get moved.
pvmove works as follows:
1. A temporary 'pvmove' logical volume is created to store details of all the data movements required.
2. Every logical volume in the volume group is searched for contiguous data that need moving according to the command line arguments. For
each piece of data found, a new segment is added to the end of the pvmove LV. This segment takes the form of a temporary mirror to copy
the data from the original location to a newly-allocated location. The original LV is updated to use the new temporary mirror segment in
the pvmove LV instead of accessing the data directly.
3. The volume group metadata is updated on disk.
4. The first segment of the pvmove logical volume is activated and starts to mirror the first part of the data. Only one segment is mir-
rored at once as this is usually more efficient.
5. A daemon repeatedly checks progress at the specified time interval. When it detects that the first temporary mirror is in-sync, it
breaks that mirror so that only the new location for that data gets used and writes a checkpoint into the volume group metadata on disk.
Then it activates the mirror for the next segment of the pvmove LV.
6. When there are no more segments left to be mirrored, the temporary logical volume is removed and the volume group metadata is updated so
that the logical volumes reflect the new data locations.
Note that this new process cannot support the original LVM1 type of on-disk metadata. Metadata can be converted using vgconvert(8).
OPTIONS
--abort
Abort any moves in progress.
-b, --background
Run the daemon in the background.
-i, --interval Seconds
Report progress as a percentage at regular intervals.
-n, --name LogicalVolume
Move only the extents belonging to LogicalVolume from SourcePhysicalVolume instead of all allocated extents to the destination phys-
ical volume(s).
EXAMPLES
To move all logical extents of any logical volumes on /dev/hda4 to free physical extents elsewhere in the volume group, giving verbose run-
time information, use:
pvmove -v /dev/hda4
SEE ALSO
lvm(8), vgconvert(8)
Sistina Software UK LVM TOOLS 2.02.44-cvs (02-17-09) PVMOVE(8)