Operating System - HP-UX
1826884 Members
3041 Online
109705 Solutions
New Discussion

Re: frecover (4305) : not enough memory for allocate

 
Anne Makino
Advisor

frecover (4305) : not enough memory for allocate

Hi All,

I am getting the following frecover message when I try to list the backup:

# frecover –x –f /dev/rmt/0m –N –v
..
-rw-rw-rw- root sys ./us13/RP5430/usr8/ano/m41/nad
-rw-rw-rw- root sys ./us13/RP5430/usr8/ano/m41/nada.bak

frecover(4305): not enough memory for allocate

The maxdsiz and shmmax parameters were increased but it didn’t help.

maxdsiz = 0x20000000
shmmax = 0x80000000

Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 4192256 Kbytes, lockable: 3726100 Kbytes, available: 3280288 Kbytes

Mb Mb Mb PCT START/ Mb
TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME
dev 8192 0 8192 0% 0 - 1 /dev/vg00/lvol2
reserve - 216 -216
total 8192 216 7976 3% - 0 -


procs memory page faults cpu
r b w avm free re at pi po fr de sr in sy cs us sy id
1 0 0 24941 763970 364 155 81 0 0 0 11 1573 64975 1405 5 5 90

If I have physical memory and swap space available, what it is wrong?

Could this problem be related to 1.75GB due to 32-bits applications? I have Cobol installed.

Thanks in advance.
4 REPLIES 4
Grayh
Trusted Contributor

Re: frecover (4305) : not enough memory for allocate

Anne Makino
Advisor

Re: frecover (4305) : not enough memory for allocate

I checked this thread and the parameter increased as I explained previously
Thank you!
Kenan Erdey
Honored Contributor

Re: frecover (4305) : not enough memory for allocate

>Could this problem be related to 1.75GB due to 32-bits applications? I have Cobol installed.

if frecover can't allocate memory above it's limit because of 32bit unix it can be. perhaps a patch fix it ?
Computers have lots of memory but no imagination
Dennis Handly
Acclaimed Contributor

Re: frecover (4305) : not enough memory for allocate

> maxdsiz = 0x20000000

You still have maxdsiz at 500 Mb. You might want to increase it to 2 Gb.

While you are at it, you should turn on pseudoswap: swapmem_on

>Could this problem be related to 1.75GB due to 32-bits applications?

Not until you set maxdsiz to 2 Gb.