ADSM-L

ANR9999D afmove.c(964) when reclaiming offsite volume ?

1998-10-23 12:00:40
Subject: ANR9999D afmove.c(964) when reclaiming offsite volume ?
From: Jon Vander Hill <jcv AT BINC DOT NET>
Date: Fri, 23 Oct 1998 11:00:40 -0500
I'm getting an error when ADSM attempts to reclaim the last few
files from an offsite volume.  I've never seen this one before
and am wondering what's up and what the appropriate procedure is
to address the problem.

config:

Sun Sparc 5 (no giggles), Solaris 2.5.1
IBM 3570 C12
ADSTAR Distributed Storage Manager for Sun Solaris
Version 2, Release 6, Level 0.15/2.15

dsmserv log:

ANR1040I Space reclamation started for volume 006847, storage pool TAPECOPY
(process number 1).
ANR2560I Schedule manager started.
ANR0402I Session 1 started for administrator JCV (SunOS).
ANR9999D afmove.c(964): Error 87 queuing storage pool volumes for offsite move
data.  Move Data processing may be incomplete.
ANR9999D afmove.c(964): Error 87 queuing storage pool volumes for offsite move
data.  Move Data processing may be incomplete.
ANR9999D afmove.c(964): Error 87 queuing storage pool volumes for offsite move
data.  Move Data processing may be incomplete.
...
ANR1163W Offsite volume 006847 still contains files which could not be moved.
ANR1041I Space reclamation ended for volume 006847.

q vol 006847 f=d

                   Volume Name: 006847
             Storage Pool Name: TAPECOPY
             Device Class Name: IBM3570
       Estimated Capacity (MB): 5,715.1
                         %Util: 0.0
                 Volume Status: Full
                        Access: Offsite
        Pct. Reclaimable Space: 100.0
               Scratch Volume?: Yes
               In Error State?: No
      Number of Writable Sides: 1
       Number of Times Mounted: 9
             Write Pass Number: 1
     Approx. Date Last Written: 09/18/1998 14:36:55
        Approx. Date Last Read: 09/11/1998 13:08:02
           Date Became Pending:
        Number of Write Errors: 0
         Number of Read Errors: 0
               Volume Location:
Last Update by (administrator): JCV
         Last Update Date/Time: 09/28/1998 14:29:44

q content 006847

Node Name                Type Filespace  Client's Name for File
                              Name
------------------------ ---- ---------- --------------------------------------
(13)                     (?)  (8)        Bitfile.4321226
(13)                     (?)  (8)        Bitfile.4321226
(13)                     (?)  (8)        Bitfile.4321453
(13)                     (?)  (8)        Bitfile.4321454
(13)                     (?)  (8)        Bitfile.4321455
(13)                     (?)  (8)        Bitfile.4321456
...
(13)                     (?)  (8)        Bitfile.4339415
(13)                     (?)  (8)        Bitfile.4339416
(13)                     (?)  (8)        Bitfile.4339417
(13)                     (?)  (8)        Bitfile.4339419
(13)                     (?)  (8)        Bitfile.4339420

I don't have any nodes named "(13)" and am not too sure what this means.

--
Jon Vander Hill, N8PAP
Jon Vander Hill, N8PAP
Senior Systems Engineer        Email: vanderhill AT berbee DOT com
Berbee Information Networks    URL:   http://www.mailbag.com/users/vanderhill
5220 Research Park Drive       Voice: (608) 288-3000 x1606
Madison, WI 53711-5377         Fax:   (608) 288-3007
<Prev in Thread] Current Thread [Next in Thread>
  • ANR9999D afmove.c(964) when reclaiming offsite volume ?, Jon Vander Hill <=