Looks like there is probably some data that is lost on that tape, unless
you have a copy storage pool...
To get around that you will want to take the recl up to 100 to pause
reclamation, then
if you have a copy storage pool,
and this tape is in the primary pool
mark the volume destroyed,
rebuild the volume from the copy pool
if you have a copy storage pool,
and this tape is in the copy pool
mark the volume destroyed,
run another backup storage pool to recreate the data on the tape...
if you do NOT have a copy storage pool,
run an "audit volume" against the tape...
fix=yes will delete the bad data
run a move data to clear the tape
resumre reclamation as normal...
hope this helps...
Dwight
Peter Duempert
<p.duempert@tu-bs To: ADSM-L AT VM.MARIST
DOT EDU
.de> cc:
Sent by: "ADSM: Subject: Space reclamation
running since 23Dec2003
Dist Stor
Manager"
<[email protected]
.EDU>
01/05/2004 11:25
AM
Please respond to
Peter Duempert
Hi TSM'ers,
here a sequence of what had happened with a
TSM-SERVER 5.1.8.1 on an IBM H70 under AIX 4.3.3-11
and 6 months old 3584-LTO2 library with 4 drives
1. SPACE RECLAMATION started as follows:
23.12.2003 03:16:14 ANR1040I Space reclamation started for volume
373ABW, storage pool LTO_EC (process number 254).
23.12.2003 03:16:14 ANR1044I Removable volume 373ABW is required for
space reclamation.
23.12.2003 03:16:16 ANR1142I Moving data for collocation cluster 1 of
23.12.2003 03:39:22 ANR8337I LTO volume 373ABW mounted in drive LTO_3
(/dev/rmt4).
23.12.2003 03:41:32 ANR1142I Moving data for collocation cluster 2 of
6412 on volume 373ABW.
2. Reading errors started
rzds3# grep ANR8359 q.actl.20031223.redu
23.12.2003 19:51:55 ANR8359E Media fault detected on LTO volume
373ABW in drive LTO_3 (/dev/rmt4) of library 3584.
23.12.2003 21:32:05 ANR8359E Media fault detected on LTO volume
373ABW in drive LTO_3 (/dev/rmt4) of library 3584.
... and continued
rzds3# grep ANR8359 q.actl.2003122*.redu | wc -l
28
rzds3# grep ANR8359 q.actl.2003123*.redu | wc -l
10
rzds3# grep ANR8359 q.actl.200401*.redu | wc -l
14
Until today I got 52 READING-errors, which show up as well in the
AIX-based "errpt.
3. The current state
tsm: DS3>q proc 254
Process Process Description Status
Number
-------- --------------------
-------------------------------------------------
254 Space Reclamation Volume 373ABW (storage pool LTO_EC),
Moved Files:
907296, Moved Bytes: 30,652,121,214,
Unreadable
Files: 558, Unreadable Bytes:
22,733,876.
Current Physical File (bytes): None
Current
input volume: 373ABW.
Current output volume:
368ABW.
tsm: DS3>q vol 373ABW f=d
Volume Name: 373ABW
Storage Pool Name: LTO_EC
Device Class Name: LTOCL
Estimated Capacity (MB): 181,698.7
Pct Util: 12.9
Volume Status: Full
Access: Read-Only
Pct. Reclaimable Space: 90.2
Scratch Volume?: Yes
In Error State?: No
Number of Writable Sides: 1
Number of Times Mounted: 497
Write Pass Number: 1
Approx. Date Last Written: 29.10.2003 10:31:42
Approx. Date Last Read: 05.01.2004 17:37:16
Date Became Pending:
Number of Write Errors: 0
Number of Read Errors: 53
Volume Location:
Last Update by (administrator):
Last Update Date/Time: 08.07.2003 06:53:37
tsm: DS3>q actlog begint=18:00 s=ANR1142I
Date/Time Message
--------------------
----------------------------------------------------------
05.01.2004 18:00:58 ANR1142I Moving data for collocation cluster 2845
of 6412
on volume 373ABW.
05.01.2004 18:06:05 ANR1142I Moving data for collocation cluster 2846
of 6412
on volume 373ABW.
05.01.2004 18:09:36 ANR1142I Moving data for collocation cluster 2847
of 6412
on volume 373ABW.
4. What to do next ?
1. Wait until the tape is processed with its 6412 clusters and get
the missing data from the copy-tapes ?
2. Can't wait so long because the impact on TSM's DB is very bad,
i.e. I get only 50% of the normal throughput AND 2 tape-drives
are kept for another 2 weeks, i.e.
HALT & RESTAT the server and hope for some positive effect ?
3. Any better idea ?
With some hope for good response and a HAPPY, HEALTHY NEW YEAR
--
MfG / Ciao - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Peter Dümpert Email: p.duempert AT tu-bs DOT
de
Rechenzentrum der Technischen Universität Fax : ++49/531/391-5549
D 38092 Braunschweig Tel : ++49/531/391-5535
|
