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
LEARN ABOUT HPUX
vxdestroy_lvmroot
vxdestroy_lvmroot(1M) vxdestroy_lvmroot(1M)
NAME
vxdestroy_lvmroot - remove LVM root disk and associated LVM volume group
SYNOPSIS
vxdestroy_lvmroot [-v] [-b] lvm_root_disk
DESCRIPTION
The vxdestroy_lvmroot command tears down and removes the LVM volume group associated with the specified physical disk. This is done by
removing the volumes in the volume group and then removing the volume group.
OPTIONS
-b Invokes the setboot command to change the primary boot disk to the VxVM root disk from which the system was booted (if the pri-
mary boot disk is not already set to this disk). The alternate boot device remains unchanged. If the -v option is also speci-
fied, the settings of the primary and alternate boot devices are displayed.
-v Outputs verbose messages including a timestamp that indicates major operations being performed.
ARGUMENTS
lvm_root_disk
Specifies the device name of the LVM root disk that is to be destroyed, along with its entire volume group.
EXAMPLES
This example shows the vxdestroy_lvmroot command invoked in its simpliest form:
/etc/vx/bin/vxdestroy_lvmroot c5t1d0
# /etc/vx/bin/vxdestroy_lvmroot -v -b c3t0d0
Are you sure about destroying c3t0d0 (imported on VG /dev/vg02) ? YES
vxdestroy_lvmroot 06:02: Tearing down /dev/vg02 on device c3t0d0
vxdestroy_lvmroot 06:02:
Unmounting and removing any volumes associated with /dev/vg02
vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol1
vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol2
vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol3
vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol4
vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol5
vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol6
vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol7
vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol8
vxdestroy_lvmroot 06:02: Removing Volume Group /dev/vg02
vxdestroy_lvmroot 06:02: Removing device files in /dev/vg02
vxdestroy_lvmroot 06:02: Removing LVM Physical Volume c3t0d0
vxdestroy_lvmroot 06:02: Removing LVM Physical Volume c1t1d3
vxdestroy_lvmroot 06:02: Removing LVM Physical Volume c1t1d4
vxdestroy_lvmroot 06:02: Removing LVM Physical Volume c1t1d5
vxdestroy_lvmroot 06:03: Current setboot values:
vxdestroy_lvmroot 06:03: Primary: 0/0/6/0/0.0.0
vxdestroy_lvmroot 06:03: Alternate: 0/0/1/0/0.1.0
vxdestroy_lvmroot 06:03:
Making disk c0t1d0 (0/0/1/0/0.1.0) the primary boot disk
vxdestroy_lvmroot 06:03:
Removal of device c3t0d0, volume group /dev/vg02 was successful
SEE ALSO
cpio(1), dd(1), fsck(1M), setboot(1M) vxbootsetup(1M) vxcp_lvmroot(1M) vxres_lvmroot(1M)
VxVM 5.0.31.1 24 Mar 2008 vxdestroy_lvmroot(1M)