Yeah, for us dsmc would grow past 3GB over a couple days and then die
because of the 32-bit virtual address space limit. Our solution was to
educate users to avoid putting lots of files in one directory, and if
there was a real need to notify us so we can exclude them in advance
with exclude.dir.

On 07/15/10 07:02, Wolfgang J Moeller wrote:

Skylar Thompson wrote:

I ran into something similar on RHEL4 when dealing with directories with
lots of files (11 million in one of them - so many that ext3 b-tree
indexing failed). I think even with MEMORYEFFICIENTBACKUP enabled, the
client will still need to allocate enough memory to handle one directory
at a time. Do you have any directories like that?

No, apart from a rather "standard" root file system - which accounts for
over 300k of the ~500k files involved, and typically makes for ~150 MB
"dsmc" memory consumption - the other (pretty large) files are evenly
spread over>20k directories.
And did you ever see _cumulative_ memory growth (aka "memory leak"?).

There got to be something pretty weird with this machine ...
I'm still working with TSM support.

--
-- Skylar Thompson (skylar2 AT u.washington DOT edu)
-- Genome Sciences Department, System Administrator
-- Foege Building S048, (206)-685-7354
-- University of Washington School of Medicine