Operating System - HP-UX
1827224 Members
2211 Online
109716 Solutions
New Discussion

Copy physical extents from corrupt lvol

 
Cresswell Williams
Frequent Advisor

Copy physical extents from corrupt lvol

Hi Experts

I extended a the lvol over to a faulty disk, unkown to me a the time. Did the lvextend, but the extendfs did not complete successfully. The disk failed, now the lvol is corrup.

If i do a lvdisplay on that lvol, it shows my data is still "current", and I have tried all formats of fsck known to man, ut i still cannot mount the lvol.

Now is there a way to copy off all the blocks off the lvol to another location?? I tried dd with no success.

Any ideas???
4 REPLIES 4
Mridul Shrivastava
Honored Contributor

Re: Copy physical extents from corrupt lvol

>> I extended a the lvol over to a faulty disk, unkown to me a the time. Did the lvextend, but the extendfs did not complete successfully. The disk failed, now the lvol is corrup.

If extendfs failed that means you fs size is still the old one. Then you could try reducing the lvol from that faulty disk and then try mounting the filesystem after fsck.

Another option could be to move the data to another good PV using pvmove.
Time has a wonderful way of weeding out the trivial
Cresswell Williams
Frequent Advisor

Re: Copy physical extents from corrupt lvol

Thanks for your reply.

I used pvmove -n /dev/vg00/lvol6 but it gave me I/O Errors.

How can I restor /opt from the installation media? That seems like a viable option, excuse the pun....hahaha

Thanks in advance
Mridul Shrivastava
Honored Contributor

Re: Copy physical extents from corrupt lvol

I don't think that you can recover /opt from installation media since you might have installed new softwares, applications etc after standard installation.

You could try recovery from ignite backup , provided you have one.
Time has a wonderful way of weeding out the trivial
Rasheed Tamton
Honored Contributor

Re: Copy physical extents from corrupt lvol

If you do not have an ignite or another backup the next possibility is a mirror disk - if you have one. But if you have not removed the mirror before the problem happened then the data might be already synced.

Did you use -o full option of fsck
fsck -F vxfs -o full -Y

man fsck_vxfs