ADSM-L

Re: dsmscoutd running too long

2004-02-04 10:34:31
Subject: Re: dsmscoutd running too long
From: Ian Smith <ian.smith AT COMPUTING-SERVICES.OXFORD.AC DOT UK>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 4 Feb 2004 15:33:57 +0000
Mark,

check out the Maxcandidates value for the HSM-managed filesystem
It is an option given to dsmmigfs and specifies the number of migration
candidates dsmscoutd looks for in any one pass over the filesystem.
The range of values is 9 - 9,999,999 (!!) with a default of 10,000 - which
sounds like it's too high for you.

Of course, by not migrating all the candidate files, you may find that
the occupancy of the filesystem rises to trip the automigration threshold.
This may or may not be what you require. You will have to monitor and reset
the migration parameters on this FS quite carefully, according to patterns
of use on it.

HTH
-------------------------------------------------------------------
Ian Smith
Oxford University Computing Services, Oxford, UK.
-------------------------------------------------------------------


~>
~>Does anyone have any suggestions that would reduce the time it takes the scout
daemon to produce a candidates list on a HSM file system that contains a large
number of files ?
~>
~>We currently have the candidatesinterval option at 12, however it takes
approximately 8 to 10 hours for the scout process to complete. So in effect, the
scoutd process is just about running all of the time. Other Details below:
~>
~>Client OS: AIX 4.3.3
~>TSM Client Version: 5.1
~>Server OS: AIX 5.1
~>The HSM managed file system has approximately 750000 files all under a single
directory.
~>
~>
~>
~>
~>
~>
~>Thanks,
~>Mark.

<Prev in Thread] Current Thread [Next in Thread>