Operating System - HP-UX
1833780 Members
2257 Online
110063 Solutions
New Discussion

Re: pvmove crashed - lv can not be modified anymore !

 
SOLVED
Go to solution
Dr. Peer-Joachim Koch
Frequent Advisor

pvmove crashed - lv can not be modified anymore !

Hi,

our file server is a l-class running HPUX 11.00
(latest patches). Using 2 HBA within a SAN enviroment 2 EMC FC4700 are attached (~10TB).

On friday I tried to free a LUN using
pvmove -v lvolXXX /dev/dsk/xxxx /dev/dsk/yyyy

(I've used the command before for many times without any problems). However, this time
the storage prozessor handling the lvolXXX
crashed and the pvmove died.

The file system is working, but I can not move
the remaining extends (60pv)from the /dev/dsk/xxxx to the /dev/dsk/yyyy.
The error messages is:
Transferring logical extents of logical volume "/dev/vg01/lv_LNX_Local"...
pvmove: Couldn't update the contents of logical extent:
I/O error
No syslog or anything else. I tried to umount the file system -> device busy.

What can I do to make this lvol useable again ?

I can still use the volume group, but I can not
work with this particular lv!

Thanks for your help !!

Bye, Peer

peko
5 REPLIES 5
Bharat Katkar
Honored Contributor

Re: pvmove crashed - lv can not be modified anymore !

Hi peer,
can you trace the process and kill it.

# ps -ef | grep "pvmove -v lvolXXX /dev/dsk/xxxx /dev/dsk/yyyy"

Make sure you are killing the right process.

And then try removing PV again.

Regards,
You need to know a lot to actually know how little you know
Dr. Peer-Joachim Koch
Frequent Advisor

Re: pvmove crashed - lv can not be modified anymore !

Hi,

there is no process running. Nothing related to the pvmove.

bash-2.03# lvdisplay -v /dev/vg01/lv_LNX_Local | more
--- Logical volumes ---
LV Name /dev/vg01/lv_LNX_Local
VG Name /dev/vg01
LV Permission read/write
LV Status available/syncd
Mirror copies 2
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 41600
Current LE 1300
Allocated PE 1302
Stripes 0
Stripe Size (Kbytes) 0
Bad block NONE
Allocation non-strict
IO Timeout (Seconds) default

--- Distribution of logical volume ---
PV Name LE on PV PE on PV
/dev/dsk/c14t0d1 1300 3840
/dev/dsk/c6t0d7 60 60

--- Logical extents ---
LE PV1 PE1 Status 1 PV2 PE2 Status 2 PV3 PE3 Status 3
00000 /dev/dsk/c6t0d7 00000 current PX_NOPV 00000 current PX_NOPV 00000 current


01237 /dev/dsk/c14t0d1 05830 current PX_NOPV 00000 current PX_NOPV 00000 current
01238 /dev/dsk/c14t0d1 05831 current /dev/dsk/c14t0d1 05832 current PX_NOPV 00000 current
01239 /dev/dsk/c14t0d1 05833 current /dev/dsk/c14t0d1 05834 current PX_NOPV 00000 current
01240 /dev/dsk/c14t0d1 05835 current PX_NOPV 00000 current PX_NOPV 00000 current


Bye, Peer
peko
Robert-Jan Goossens
Honored Contributor
Solution

Re: pvmove crashed - lv can not be modified anymore !

Hi Peer,

Check this doc.

Document description: Panic Hang On EMC Disk Array; Attempt To Migrate With pvmove(1M)
Document id: KBRC00010642

http://www4.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000064209290

Regards,
Robert-Jan
Dr. Peer-Joachim Koch
Frequent Advisor

Re: pvmove crashed - lv can not be modified anymore !

Thank's a lot.
The lvreduce seem's to fix the problem.
The pvmove is running now again to move
the remaning pv to the new location.

Thank you ! Great.

Bye, Peer
peko
Dr. Peer-Joachim Koch
Frequent Advisor

Re: pvmove crashed - lv can not be modified anymore !

OK,

I could move the remaing extends. But I can not
umount the file system. I stop the nfs export
tried fuser -cu MOUNTPOINT (nothing), but can not umount it...

Any help ?

Bye, Peer
peko