As long as I was on V3R1, I would see the system hang if anyone did a "q fi
or q node" while expiration was running.  The only solution was to restart
the server.  I wouldn't be surprised if something similar is at work in
your case.


At 04:54 PM 1/22/2001 +0100, you wrote:

I've run into a problem and I would be very obliged if someone has an idea
what
I could  do about it:

ADSM Server for AIX-RS/6000 - Version 3, Release 1, Level 2.20

seems to be in a strange state and nomore doing what its expected to do.

dsmadmc shows the following informations:

adsm> q log
Available Assigned   Maximum   Maximum    Page     Total      Used   Pct  Max.
    Space Capacity Extension
Reduction    Size    Usable     Pages  Util   Pct
     (MB)     (MB)      (MB)      (MB)
(bytes)     Pages                  Util
--------- -------- --------- --------- ------- --------- --------- ----- -----
      248      248         0       240   4.096    62.976       773   1,0
10,0

adsm> q db
Available Assigned   Maximum   Maximum    Page     Total      Used   Pct  Max.
    Space Capacity Extension
Reduction    Size    Usable     Pages  Util   Pct
     (MB)     (MB)      (MB)      (MB)
(bytes)     Pages                  Util
--------- -------- --------- --------- ------- --------- --------- ----- -----
    2.288    1.476       812       244   4.096   377.856   247.144  65,0
79,0

sofar anything  normal.
====================================

adsm> q sess
  Sess Comm.  Sess     Wait   Bytes   Bytes Sess  Platform Client Name
Number Method State    Time    Sent   Recvd Type
------ ------ ------ ------ ------- ------- ----- --------
--------------------
 2.072 Tcp/Ip Run      0 S   88,0 M 339,0 M Node  WinNT    ACLUSTER
 2.119 Tcp/Ip Run      0 S      124     131 Admin AIX      ADMIN
 2.120 Tcp/Ip Run      0 S    5,0 K     359 Admin AIX      ADMIN
 2.121 Tcp/Ip Run      0 S    9,0 K     462 Admin AIX      ADMIN
 2.122 Tcp/Ip Run      0 S    9,0 K     657 Admin AIX      ADMIN
 2.126 Tcp/Ip Run      0 S  286,0 K     511 Admin AIX      ADMIN

## sessions 2072, 2119...2122 have been cancelled however they continue to
hang
around
## The sessions arose from dsmadmc commands that would not finish and were
terminated with ^c
## such commands are
## q stg
## q vol

adsm> q pr
 Process Process Description  Status
  Number
-------- --------------------
-------------------------------------------------
      95 DELETE FILESPACE     Cancel in Progress.
      96 Database Backup      Cancel pending.
## Both processes were still executing showing no errors when the problem
first
came up
## process status showed around 115k files deleted (prior to my cancel pr 95
request)
## process 96 was an incremental backup of the database with the last
message in
the actlog that the output volume was dismounted

Trying to solve the problem (q vol, q stg no more responding) I subsequently
cancelled processes and sessions.
However processes did not end, sessions did not terminate.

I have not yet tried to halt the server.
(I am afraid the halt might hang as well since the processes/sessions do not
terminate)
A suspected reason for the problem is that a high volume of incremenatal
backup
data may have been coming in while the delete filespace for a different
node was
running.