dump area shrunk to end at firmware access boundary

[Houston Kemper]

Good afternoon all,

I received the message in the subject field after I had created a dump device and executed a 'crashconf -ar'.

Any thoughts on what would cause something like this?

Thanks

[Gadura Praveen]

Houston,

The dump area has to lie within the first 2 GB of the physical volume . For a system with high density memory board , a 4GB dump logical volume is supported. The possible cause of the message could be that some extents used for configured dump do not lie within the first 2GB ( or 4 GB ) of the physical volume.

Hope this helps !!

[Houston Kemper]

Forgive my ignorance, but this sounds a bit confusing...

Our total memory is 12Gb, how would we be able to dump across six disks and ensure that we consume only the first 2Gb of space when using Jamica disks?

Thanks

[Gadura Praveen]

Houston,

If your are using high density memory ( check warning section of man on lvlnboot ) you can select three disks out of the six to hold the dump. Make sure that no lvols already exist on these disks and create a 4 GB dump space on each one of them.
EX. # lvcreate -C y -r n -n lv_dump1 /dev/vg00
# lvextend -L 4000 /dev/vg00/lv_dump1 "dsk1"
# lvlnboot -d /dev/vg00/lv_dump1

repeat the above for dump2 and dump3 on disk2 and disk3 respectively. You can also use this dump space as swap but keeping swap seperate from dump is recommended. You can create other lvols on the disks after the dump lvols are created.

Good luck !!

Praveen