fbackup error

[jh_yang]

Hi,
Got the error message:
fbackup(9999): Not enough space
fbackup(1504): could not open directory `.' (/u06/docdata01/1357)
fbackup(9999): Not enough space
fbackup(1504): could not open directory `.' (/u06/docdata01/1358)
fbackup(1702): out of virtual memory

Does that mean the backup exceeded the capacity of the tape? or it's something else.

David

[Sridhar Bhaskarla · Accepted solution]

Hi,

Out of virtual memory combined with "Not enough space' errors indicate that you are running out ot swap space.

Do a 'swapinfo -t' and see if the total utilized is not near 100%. If so, then you will need to add more swap.

-Sri

[Steven E. Protter]

You appear to be all out of swap space.

swapinfo -tam

Swap must be at least 50% of RAM and a system can run efficiently up to twice RAM.

If you are at or beyond swap being twice RAM you need more memory.

See my performance collection script.

SEP

[jh_yang]

Is there a formula to calculate how much swap size required for backup X GB? I am planning to split the fbackup into 2 sessions to reduce the volume of 1 session. Will it work?

David

[Sridhar Bhaskarla]

Hi David,

Your problem is due to running out of 'swapspace' and not that your fbackup session is causing the swapspace to run out.

There isn't a fixed formula for configuring the swap space. There is a kernel parameter called "swapmem_on". If you enable it, then it is ok if you configure your swap equal to the size of your Physical Memory. If you do not have it enabled, then a general rule is to configure two times the physical memory. Remember that enabling this parameter does not really use memory as swap. It is only for accounting purposes that the system will think it has more virtual memory. 'kmtune -l -q swapmem_on' will tell you if it is on or not.

However, it depends on the application you run. You will need to constantly monitor your 'swapinfo -t' output.

-Sri

[jh_yang]

The fbackup was setup to run @ 00:15 while no other activity going on. Correct me if my understanding is not correct: fbackup kicked off and started to use swap, once there is no more swap space left, fbackup failed.

Server conf: D270, HPUX 10.20
512MB memory, 1G swap.
swapmemon=1

Again, split the fbackup into 2 jobs will help or not?

David

[Sridhar Bhaskarla]

HI David,

Can you post your 'swapinfo -tam' output?. Also, post the following to help troubleshooting further.

HP hardware model, OS, tape drive, how it is connected, kernel parameters (all) along with 'swapinfo -tam'.

-Sri

PS: Please do not allot points until your problem is completely solved. In this case, I don't think your issue is resolved yet.

[jh_yang]

Mb Mb Mb PCT START/ Mb
TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME
dev 512 10 502 2% 0 - 1 /dev/vg00/lvol2
dev 516 9 507 2% 0 - 1 /dev/vg00/lvol9
reserve - 141 -141
memory 379 305 74 80%
total 1407 465 942 33% - 0 -

Model: 9000/861/D270
OS: 10.20
Tape: DLT 7000
Connection: FW SCSI
Kernel parameter:
maxfiles 512
maxswapchunks 850
maxuprc 160
msgmax 32768
msgmnb 65535
msgmni 128
msgseg 7168
msgssz 32
msgtql 258
ninode 952
nproc 1600
nstrpty 60
semmni 256
semmns 512
shmmax 0X40000000
shmmni 256
num_tachyon_adapters 5
max_fcp_reqs 512


David