I don't know how it happened,but it did and I just want to know if I can clean it up.
I was doing pvmoves to new disks, doing something like;
pvmove -n /dev/vgdb1/lvd1 /dev/dsk/c4t5d6 /dev/dsk/c7t8d9
Only I had a script that ran it because there were 8 lvols and it would run longer than I wanted to be at work.
Next day, nohup.out shows everything completed successfully. BUT, when I do a pvdisplay on the new disks I see two lvols on one disk instead of the one for one I was shooting for.
My question is can I do another pvmove to move the partial extents that are on the wrong disk to the right disk? The extents would be out of order. i.e.
PV Name /dev/dsk/c5t9d4
PV Name /dev/dsk/c8t9d4 Alternate Link
Total PE 16381
Free PE 0
/dev/vgdb1/lvd7 11089 11089
/dev/vgdb1/lvd8 5292 5292
PV Name /dev/dsk/c8t9d5
PV Name /dev/dsk/c5t9d5 Alternate Link
Total PE 16381
Free PE 6048
/dev/vgdb1/lvd8 10333 10333
Can I pvmove the lvd8 extents on c5t9d4 to c8t9d5? will there be any problems?
Thanks,
NJ
Note: If you are the author of this question and wish to assign points to any of the answers, please login first.For more information on assigning points ,click
here
Right, I was planning on doing the pvmove from c5t9d4 to c8t9d5, but just the 5292 lvd8 extents. I was concerned with the sequence of the extents. Does it matter?
It started with the first pvmove, two lvols ended up with extents on one disk and it sort of cascaded from there. Instead of moving extents from one disk to another specific disk, it put 756 extents of the next lvol on also.
I would have to move each one down a disk inorder to free up the space to move the previous. I probably didn't make that real clear. I'll attach a file showing the disks and extents.
Well, not getting any confidence building suggestions I decided to do the pvmoves of the errant extents onto another disk and then back to the rightful disk. One lvol at a time.
Printable version
