08-22-2019
You have lost access to a disk, hdisk37
How is this provided? If it's a real disk, then it's broken. If it's SAN provided, then something has gone wrong in the provision.
If you can get the disk back online, you might get away with syncvg -l cpsabcd2lv to re-mirror, but you need the hardware (however provided) to be sorted first.
I notice that loglv00 is not mirrored. I would suggest getting that done. If you had lost hdisk36 then would be in real trouble. As it is, LVM is coping.
Kind regards,
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
PVCK(8) System Manager's Manual PVCK(8)
NAME
pvck - check physical volume metadata
SYNOPSIS
pvck [-d|--debug] [-h|--help] [-v|--verbose] [--labelsector] PhysicalVolume [PhysicalVolume...]
DESCRIPTION
pvck checks physical volume LVM metadata for consistency.
OPTIONS
See lvm for common options.
--labelsector sector
By default, 4 sectors of PhysicalVolume are scanned for an LVM label, starting at sector 0. This parameter allows you to specify a
different starting sector for the scan and is useful for recovery situations. For example, suppose the partition table is corrupted
or lost on /dev/sda, but you suspect there was an LVM partition at approximately 100 MB. This area of the disk may be scanned by
using the --labelsector parameter with a value of 204800 (100 * 1024 * 1024 / 512 = 204800):
pvck --labelsector 204800 /dev/sda
Note that a script can be used with --labelsector to automate the process of finding LVM labels.
SEE ALSO
lvm(8), pvcreate(8), pvscan(8) vgck(8)
Sistina Software UK LVM TOOLS 2.02.67(2) (2010-06-04) PVCK(8)