Last year, I had reported ...
on a (real big!) x86_64 machine, with freshly installed SuSE SLES 10.3,
scanning a mere ~500k files (and typically saving 10,000 per run),
dsmc has been found to consume about 1.3 GByte of virtual memory
per single run. This is about tenfold from what you'd
Thanks for reporting back. This is something we've struggled with too.
I'll have to give nscd a shot.
On 02/ 1/11 01:16 AM, Wolfgang J Moeller wrote:
Last year, I had reported ...
on a (real big!) x86_64 machine, with freshly installed SuSE SLES 10.3,
scanning a mere ~500k files (and
Grigori Solonovitch wrote:
I think there is a mistake in version. If you mention 6.2.1.0, try to install
6.2.1.1.
There are some bugs related to memory allocation which are fixed in 6.2.1.1.
At least, client 6.2.1.1 helped to fix my problems with memory allocation.
Sorry for the typo.
Robert Clark writes:
Dumb question, but have you examined the client to see if there are any
circular links?
(For example a link low in the tree that points higher in the tree.)
To a first approximation, this doesn't seem to be the problem -
I can see the extensive memory usage even with a
: Dist Stor Manager [ads...@vm.marist.edu] On Behalf Of Wolfgang J
Moeller [moel...@gwdg.de]
Sent: Friday, July 16, 2010 1:30 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Excessive memory consumption by 5.5 Linux client on SLES
10.3 x86_64
Robert Clark writes:
Dumb question, but have you
Subject: Re: [ADSM-L] Excessive memory consumption by 5.5 Linux client on SLES
10.3 x86_64
Robert Clark writes:
Dumb question, but have you examined the client to see if there are any
circular links?
(For example a link low in the tree that points higher in the tree.)
To a first
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
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.
consumption by 5.5 Linux client on SLES 10.3
x86_64
Sent by:
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
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
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.
Good morning,
on a (real big!) x86_64 machine, with freshly installed SuSE SLES 10.3,
scanning a mere ~500k files (and typically saving 10,000 per run),
dsmc has been found to consume about 1.3 GByte of virtual memory
per single run. This is about tenfold from what you'd expect ...
And even
11 matches
Mail list logo
