ADSM-L

[ADSM-L] consider Mount Wait & Mount Retention

2008-07-20 00:04:59
Subject: [ADSM-L] consider Mount Wait & Mount Retention
From: Pavel Sitnikov <SitnikovPG AT URALSIBBANK DOT RU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Sat, 19 Jul 2008 17:30:58 +0600
Hi!
1)would you recommend what kind of "schedmode" better: prompted or 
polling?
2) when sched in prompted mode how it start after "Schedule prompter 
contacting..."? For example we have Schedule Randomization Percentage : 
10, duration=30, durunits=minutes. We have 4 drives in 3584. All drives 
busy. Sched started and wait 30 min. If in this period one drive released 
then sched start immediatly without randomization (3 min in our example) 
or wait 1,2 or 3 min? 
If we have sheds on some clients with status "in progress" too many times 
and when stop all tsm process on problem clients(scheds,dsmsta) this we 
have on tsm server side:
В драйвах висели две ленты A00022L4 и A00018L4
q mount
ANR8379I Mount point in device class LTO4 is waiting for the volume mount 
to complete, status: WAITING FOR VOLUME.
ANR8331I LTO volume A00022L4 is mounted R/W in drive DRIVE4 (mt3.0.0.3), 
status: DISMOUNTING.
ANR8379I Mount point in device class LTO4 is waiting for the volume mount 
to complete, status: WAITING FOR VOLUME.
ANR8379I Mount point in device class LTO4 is waiting for the volume mount 
to complete, status: WAITING FOR VOLUME.
ANR8380I LTO volume A00018L4 is mounted R/W in drive DRIVE2 (mt2.0.0.3), 
status: RETRY DISMOUNT FAILURE.
ANR8379I Mount point in device class LTO4 is waiting for the volume mount 
to complete, status: WAITING FOR VOLUME.
ANR8334I         6 matches found.

' A00018L4 Allocated to dcfintest-sa and A00022L4 Allocated to DCFINDVP-SA
kill -15 all tsm proc on dcfintest

q mount
ANR8379I Mount point in device class LTO4 is waiting for the volume mount 
to complete, status: WAITING FOR VOLUME.
ANR8331I LTO volume A00022L4 is mounted R/W in drive DRIVE4 (mt3.0.0.3), 
status: DISMOUNTING.
ANR8379I Mount point in device class LTO4 is waiting for the volume mount 
to complete, status: WAITING FOR VOLUME.
ANR8379I Mount point in device class LTO4 is waiting for the volume mount 
to complete, status: WAITING FOR VOLUME.
ANR8329I LTO volume A00020L4 is mounted R/W in drive DRIVE2 (mt2.0.0.3), 
status: IDLE.
ANR8334I         5 matches found.

' A00020L4 Allocated to DCFINTECH-SA
kill -15 all tsm proc on dcfindvp

q mount
ANR8379I Mount point in device class LTO4 is waiting for the volume mount 
to complete, status: WAITING FOR VOLUME.
ANR8380I LTO volume A00022L4 is mounted R/W in drive DRIVE4 (mt3.0.0.3), 
status: RETRY DISMOUNT FAILURE.
ANR8379I Mount point in device class LTO4 is waiting for the volume mount 
to complete, status: WAITING FOR VOLUME.
ANR8379I Mount point in device class LTO4 is waiting for the volume mount 
to complete, status: WAITING FOR VOLUME.
ANR8334I         4 matches found.
q mount
ANR8376I Mount point reserved in device class LTO4, status: RESERVED.
ANR8329I LTO volume A00022L4 is mounted R/W in drive DRIVE4 (mt3.0.0.3), 
status: IDLE.
ANR8329I LTO volume A00024L4 is mounted R/W in drive DRIVE3 (mt1.0.0.3), 
status: IDLE.
ANR8334I         3 matches found.
q mount
ANR8376I Mount point reserved in device class LTO4, status: RESERVED.
ANR8334I         1 matches found.

3)would you recommend optimum Mount Wait & Mount Retention parameters?
<Prev in Thread] Current Thread [Next in Thread>