rootvg, migratepv, partition map file problems

[bi]

I am having problems with rootvg. When trying to do anything with LVM, I get allocp errors. OS level is 5.3 TL4 SP3.

The most revealing error I received was when I was trying to do a migratepv on one of the LVs. These are the errors:

# migratepv -l hd3 hdisk0 hdisk4

0516-408 allocp: Illegal logical volume identifier value.

0516-132 lmigratelv: Incorrect entry in partition map file.

0516-134 lmigratelv: Received: 000f8c0a57adabfd 154



0516-136 lmigratelv: Error reading input map.

0516-812 migratepv: Warning, migratepv did not completely succeed;

all physical partitions have not been moved off the PV.

[root@chip]/CSS/scripts

Does anyone know what the "partition map file" is in the 0516-132 error? Can it be repaired manually? Has anyone encountered this before? Is there any way out of this short of rebuilding the entire system?

 

[khalidaaa]

Have you checked the /tmp filesystem? Is it full?

 

[p5wizard]

A partition map file is just a temp file (contains pv names and pp numbers) that - in this instance - was created by the migratepv command for use by the low-level commands invoked by migratepv.

Please - to start with - show

lsvg rootvg
lsvg -p rootvg
lsvg -l rootvg



HTH,

p5wizard

 

[bi]

Thanks.

[tt]$ lsvg rootvg
VOLUME GROUP: rootvg VG IDENTIFIER: 000fb1aa00004c00000001104ee9c3d5
VG STATE: active PP SIZE: 64 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 1084 (69376 megabytes)
MAX LVs: 256 FREE PPs: 826 (52864 megabytes)
LVs: 13 USED PPs: 258 (16512 megabytes)
OPEN LVs: 11 QUORUM: 1
TOTAL PVs: 2 VG DESCRIPTORS: 3
STALE PVs: 0 STALE PPs: 0
ACTIVE PVs: 2 AUTO ON: no
MAX PPs per VG: 32512
MAX PPs per PV: 1016 MAX PVs: 32
LTG size: 128 kilobyte(s) AUTO SYNC: no
HOT SPARE: no BB POLICY: relocatable
$ lsvg -p rootvg
rootvg:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk1 active 542 401 109..00..75..108..109
hdisk0 active 542 425 77..23..108..108..109
$ lsvg -l rootvg
rootvg:
LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
hd5 boot 1 2 2 closed/syncd N/A
hd6 paging 8 16 2 open/syncd N/A
hd8 jfslog 1 2 2 open/syncd N/A
hd4 jfs 1 2 2 open/syncd /
hd2 jfs 34 68 2 open/syncd /usr
hd9var jfs 3 6 2 open/syncd /var
hd3 jfs 2 4 2 open/syncd /tmp
gss_loc_lv jfs 15 30 2 open/syncd /GSS
hd10opt jfs 19 38 2 open/syncd /opt
backup jfs2 32 64 2 open/syncd /backup
loglv00 jfs2log 1 2 2 closed/syncd N/A
hd7 dump 12 12 1 open/syncd N/A
hd7x dump 12 12 1 open/syncd N/A[/tt]

 

[p5wizard]

rootvg only has hdisk0 and hdisk1, and you are trying to migratepv to hdisk4 ???

first you need to

extendvg rootvg hdisk4

(make hdisk4 a member PV of rootvg - if thst PV is not in a different VG that is... migratepv only works within the same VG)


HTH,

p5wizard

 

[bi]

Sorry. That was another system that also has the same problem with LVM. I only showed the migratepv error because it seemed to be the most descriptive.

 

[p5wizard]

Well, then please show exact error you encounter on this system, and exact command you try to run...

At first glance, I don't see anything wrong with this rootvg...




HTH,

p5wizard

 

[bi]

OK. Trying to add 1 PP to a filesystem:

0516-408 allocp: Illegal logical volume identifier value.

 

[p5wizard]

Which filesystem? Which LV? I'm answering half-blind here...

Try this

lslv -m lvname
(show LV map)

on that LV first?


Hint: To increase /tmp FS size by one byte (=> rounded up to one PP):

chfs -asize=+1 /dev/hd3
or
chfs -asize=+1 /tmp


HTH,

p5wizard

 

[kHz]

1) chlv
2) striped lv?