System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

frecover -x -i / -f /dev/rmt/1m leads to frecover(4305): not enough memory for allocate

 
EU-Admins-UNIX
Regular Advisor

frecover -x -i / -f /dev/rmt/1m leads to frecover(4305): not enough memory for allocate

Hi

 

Trying to recover a system at DR test.  O/S has ignited and when time comes to run the frecover, we get the following:

 

frecover(4305): not enough memory for allocate

 

Please see parameter settings below, as well as other outputs.

 

System has 64GB memory, running HP-UX 11.31 patched to March 2010.

 

Regards

 

Tariq

7 REPLIES
James R. Ferguson
Acclaimed Contributor

Re: frecover -x -i / -f /dev/rmt/1m leads to frecover(4305): not enough memory for allocate

Hi:

 

If you have killed any of the 'fbackup/frecover' sessions you may have left orphaned shared memory segments holding memory.  I'd reboot if that's the case.

 

Are you using a custom 'config' file with 'readerprocesses' set to a high value (the range is 2-6 with 2, the default).  If so, try reducing that value.  The file normally resides in '/var/adm/fbackupfiles'.

 

Regards!

 

...JRF...

EU-Admins-UNIX
Regular Advisor

Re: frecover -x -i / -f /dev/rmt/1m leads to frecover(4305): not enough memory for allocate

Thanks James

 

We have rebooted, and still get the same issue.

 

there is no /var/adm/backupfiles file.

James R. Ferguson
Acclaimed Contributor

Re: frecover -x -i / -f /dev/rmt/1m leads to frecover(4305): not enough memory for allocate

Hi:

 

Do you have patch PHCO_40460 installed?  It addresses the very error you have:

 

frecover(1M) fails with an error message like
	"frecover(4305): not enough memory for allocate"
	when fbackup(1M) was used
	1. with a blocksperrecord value greater than 9765
	2. in a locale where the date starts with digits,
	like "2008 Jun 26 02:29:39 Thu"

Regards!

 

...JRF...

Re: frecover -x -i / -f /dev/rmt/1m leads to frecover(4305): not enough memory for allocate

Some things to look at:

 

1. What value do you have for the kernel parm maxdsiz?

2. Do you have patch PHCO_40460 installed - this seems to fix error conditions similar to what you describe


HTH

Duncan

Re: frecover -x -i / -f /dev/rmt/1m leads to frecover(4305): not enough memory for allocate

You have maxdsiz all the way at 4 Gb but frecover can only use 1 Gb.  (Unless you use chatr on your PA system.)

 

>you may have left orphaned shared memory segments holding memory.  I'd reboot if that's the case.

 

Any reason not to use ipcrm(1) instead of a reboot?

 

>1. What value do you have for the kernel parm maxdsiz?

 

The attached file showed 4 Gb.  With 172 Gb free.

EU-Admins-UNIX
Regular Advisor

Re: frecover -x -i / -f /dev/rmt/1m leads to frecover(4305): not enough memory for allocate

Patch added, still facing the same issue!

 

The params are set OK, way over the min required.

 

Regards

 

Tariq

Re: frecover -x -i / -f /dev/rmt/1m leads to frecover(4305): not enough memory for allocate

>Patch added, still facing the same issue!

 >The parms are set OK, way over the min required.

 

For maxdsiz, since you don't know the minimum required, you can't really say that.  But your maxssiz is reasonable, 70 Mb.

 

I suppose you could run tusc on frecover and see where it goes wrong.

Or just use top to watch the memory use and see if it gets close to 1 Gb.