Find the answer to your Linux question:
Results 1 to 4 of 4
Hi all- I have been having an issue restoring from TSM with a very large file system - millions of files - it stops examining files after 7 million plus. ...
  1. #1
    Just Joined!
    Join Date
    Jan 2009
    Posts
    3

    RedHat 3 Upd #6 - memory allocation issue

    Hi all-

    I have been having an issue restoring from TSM with a very large file system - millions of files - it stops examining files after 7 million plus.

    Here are a few details:

    From the client after using this command:

    dsmc rest -inact -subdir=yes -ifnewer -rep=yes "/data/*" "/data/"

    ...

    ANS1899I ***** Examined 7,200,456,000 files *****

    Then it stops and gives this error:

    ANS1030E The operating system refused a TSM request for memory allocation.

    From the Client dsmerror.log:

    03/19/2011 14:38:28 Realloc failed: Old addr 0xbdf90020 New Size 27262976 File restproc.cpp Line 12292

    03/19/2011 14:38:36 ANS1030E The operating system refused a TSM request for memory allocation.

    I've tried increasing the number of files in limits.conf - Linux config and increasing the RAM(8GB now) of the Vmware Virtual machine - has 2 CPU's.

    I've reinstalled TSM client - running v 5.5.0.0 now.
    Same issue with 5.3.6.

    I suspect it is still an OS issue but have no clue what to do - I can try to restore parts of the filesystem and sperate directories instead like:

    dsmc rest -inact -subdir=yes -ifnewer -rep=yes "/data/journal/*" "/data/journal/"

    This may work...but, does anyone have other ideas?
    Ever encountered this error when the Linux OS memory is exhausted by a backup client?

    I'm also trying to create a larger swap partition and tweak the TSM config file to use less memory and use more swap.

    Thx for any input.

    -P

  2. #2
    Linux Guru Rubberman's Avatar
    Join Date
    Apr 2009
    Location
    I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
    Posts
    8,974
    Is this a 32-bit system? My guess is yes, give the age of the system (RHEL 3 is now officially an "antique"). That means that the size limit of any process is 4GB, no matter how large your swap space is. While TSM is running, monitor the memory available on the system with the "free" command, or run "top". Those may help you determine whether or not you are SOL or not. I suspect you have "hit the wall" system-wise myself.

    Solutions? See if you can partition the job so that you aren't trying to analyze the entire file system space at one time. I'm not familiar with this tool, TSM, so I can only give generalities.
    Sometimes, real fast is almost as good as real time.
    Just remember, Semper Gumbi - always be flexible!

  3. #3
    Just Joined!
    Join Date
    Jan 2009
    Posts
    3
    Hi Rubberman,

    Yep - 32bit indeed.
    And the 4GB may not be enough for 10 million or more files for the Tivoli STorage Manager client ot handle.

    Yep - I partitioned or seperated out the restores - restored directories within the FS - that seems to work fine now.

    Thanks for your help and insight.

    -P

  4. #4
    Linux Guru Rubberman's Avatar
    Join Date
    Apr 2009
    Location
    I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
    Posts
    8,974
    Yes. I haven't worked with Tivoli for many years (almost 10 now), so I didn't associate the term TSM with Tivoli Storage Manager. In any case, I'm happy you have been able to move forward with this.
    Sometimes, real fast is almost as good as real time.
    Just remember, Semper Gumbi - always be flexible!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
...