ADSM-L

Storage inaccessible

2002-02-11 10:11:35
Subject: Storage inaccessible
From: Fred Johanson <fred AT MIDWAY.UCHICAGO DOT EDU>
Date: Mon, 11 Feb 2002 09:12:35 -0600
Server 4.1.5
OS AIX 4.3.3
3494 with 3590E drives all up to date on microcode, drivers, Atape, atldd, etc.

With that in mind, can someone explain to me what's going on?

At 5:05:28 Saturday afternoon offsite reclamation was running, along with
stgpool backup, on my regular weekly schedule.  A cartridge was called for,
but, from the AC log, it looks like there was no drive immediately
available.  Here is one section from the log:

02/10/2002 18:02:31  ANR0984I Process 583 for SPACE RECLAMATION started in the
                      BACKGROUND at 18:02:31.
02/10/2002 18:02:31  ANR1040I Space reclamation started for volume UC1147,
                      storage pool OFFTAPEPOOL (process number 583).
 <volume list cut>
02/10/2002 18:02:31  ANR1040I Space reclamation started for volume UC0577,
                      storage pool OFFTAPEPOOL (process number 583).
02/10/2002 18:02:42  ANR1044I Removable volume UC1171 is required for space
                      reclamation.
02/10/2002 18:02:42  ANR8324I 3590 volume UC1171 is expected to be mounted
                      (R/W).
02/10/2002 18:02:42  ANR0985I Process 583 for SPACE RECLAMATION running in the
                      BACKGROUND completed with completion state FAILURE at
                      18:02:42.
02/10/2002 18:02:42  ANR1081W Space reclamation terminated for volume UC1147 -
                      storage media inaccessible.
02/10/2002 18:02:42  ANR1042I Space reclamation for storage pool OFFTAPEPOOL
                      will be retried in 60 seconds.

This sequence of messages repeats, three times an hour, for more than
twenty four hours.
At one point, but only once, this message appears:

02/10/2002 10:27:39  ANR1229W Volume UC1171 cannot be backed up - volume is
                      offline or access mode is "unavailable" or "destroyed".


 Volume UC1171 is marked as readwrite and is present in the library.  I
have checked it out and checked it back in again, and the verify label
message and successful mount messages appear normal:

02/10/2002 14:10:01  ANR8335I 002: Verifying label of 3590 volume UC1171 in
                      drive DRIVE6 (/dev/rmt5).
02/10/2002 14:10:04  ANR8328I 002: 3590 volume UC1171 mounted in drive DRIVE6
                      (/dev/rmt5).
02/10/2002 14:10:38  ANR8427I CHECKIN LIBVOLUME for volume UC1171 in library
                      TSMLIB completed successfully.

A check from the consol of the 3494 shows that it's present, but it won't
mount for reclamation.  So I tried, yesterday and this morning, to do a MOVE:

02/11/2002 08:31:03  ANR2017I Administrator FRED issued command: MOVE DATA
                      uc1171
02/11/2002 08:31:03  ANR2232W This command will move all of the data stored on
                      volume UC1171 to other volumes within the same storage
                      pool; the data will be inaccessible to users until the
                      operation completes.
02/11/2002 08:31:04  ANR2017I Administrator FRED issued command: MOVE DATA
                      uc1171
02/11/2002 08:31:04  ANR1157I Removable volume UC1171 is required for Move
Data
                      process.
02/11/2002 08:31:04  ANR8324I 3590 volume UC1171 is expected to be mounted
                      (R/W).
02/11/2002 08:31:04  ANR1140I Move data process started for volume UC1171
                      (process ID 621).
02/11/2002 08:31:04  ANR1142I Moving data for collocation cluster 1 of 39 on
                      volume UC1171.
02/11/2002 08:33:10  ANR1144W Move data process terminated for volume UC1171 -
                      storage media inaccessible.

I have seen this phenomenon of inaccessibility before, when there is no
drive available for a migration.  At that point, the only way to get
migration to begin is by recycling the server.  That's happened twice since
installing this level of code.

Can someone please explain this???
<Prev in Thread] Current Thread [Next in Thread>