al Message-
> > From: Lindsay Morris [SMTP:[EMAIL PROTECTED]]
> > Sent: Thursday, May 31, 2001 2:15 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: adsm 3.1 and stgpool reclaim threshold
> >
> > 1. try "q actlog begind=-2 s=recla" (or maybe s=100
migration, which completes immediately - then the next
> packet does the same thing, so migration thrashes crazily.
>
> > -Original Message-
> > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> > Stephen Pole
> > Sent: Wednesday, May 30, 2
-Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> Stephen Pole
> Sent: Wednesday, May 30, 2001 11:44 PM
> To: [EMAIL PROTECTED]
> Subject: Re: adsm 3.1 and stgpool reclaim threshold
>
>
> Hi Steve,
>
> I have not seen thi
I would search the activity log for all references to the stgpool of
interest. You should see the command that does the update. Hopefully with
the time stamp you can find the culprit.
Ex: query act begind=today-1 search=some_stgpool_name
On Thu, 31 May 2001, Steve de Souza wrote:
> Hi,
>
Yet another idea,
It may well be if you have no admin command schedules there maybe another
script or something in cron that maybe doing the update as well.
I have a script is rc.shutdown that updates the storage pool levels prior to
shutdown.
The reason for this is that I have forgotten th
Hi Steve,
I have not seen this behaviour unless you have an entry in adminstrative
command schedules like the ones below:-
To check this out do the following:-
Log into the ADSM Web GUI
Select > Object View > Automation > Adminstrative Command Schedules
This will bring up the Automated comman
