ADSM-L

Re: [ADSM-L] ANS5020E Out of Archive Space?

2007-11-06 14:37:53
Subject: Re: [ADSM-L] ANS5020E Out of Archive Space?
From: "Ritter, John M" <john.ritter AT VANDERBILT DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 6 Nov 2007 13:37:23 -0600
I had a similar situation with this error.  I contacted IBM support on
this and they told me that this message can sometimes be encountered if
you are using client compression and going to a disk pool.  I don't
remember the exact details, but the idea is that TSM estimates how much
of the disk pool is needed and reserves that amount.  Later in the
session, TSM may revise its estimate of how much it needs and ask for
additional reservation.  If the unused and unreserved space in the
diskpool is insufficient to honor the reservation, you get the message,
even though you don't actually fill up the diskpool.

In my case the solution was to increase the diskpool size by about 20%,
from about 240GB to 311GB in size.  I have not encountered the error
since I did this.

John Ritter

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Jim Zajkowski
Sent: Tuesday, November 06, 2007 9:45 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: ANS5020E Out of Archive Space?

Hi folks,

I had a user try to send ~500GB to an archive.  The disk pool for
archive space is 123 GB, and there's plenty of free tape behind it.

At about 218 GB into the operation, the client threw this error:

> 11/05/2007 18:56:54 Server out of data storage space
> 11/05/2007 18:56:55 Server out of data storage space
> 11/05/2007 18:56:56 Server out of data storage space
> 11/05/2007 18:56:57 Server out of data storage space
> 11/05/2007 18:56:58 ANS5020E Server out of archive data storage space

Googling for the error reveals the unhelpful "duh it ran out of space,
call your admin."

The server actlog for that time period on the server shows nothing
unusual (TAR013 is a tape in the archivepool's migration destination.
TAR013 has plenty of space as well).

> 11/05/2007 18:54:49      ANR0514I Session 4493 closed volume
> TAR013L2. (SESSION:
>                           4493)
> 11/05/2007 18:54:51      ANR0511I Session 4493 opened output volume
> TAR013L2.
>                           (SESSION: 4493)
> 11/05/2007 18:54:53      ANR0514I Session 4493 closed volume
> TAR013L2. (SESSION:
>                           4493)
> 11/05/2007 18:56:56      ANR0403I Session 4493 ended for node WATSON
> (Linux86).
>                           (SESSION: 4493)
> 11/05/2007 18:56:58      ANE4952I (Session: 4492, Node: WATSON)
> Total number of
>                           objects inspected:   18,253 (SESSION: 4492)
> 11/05/2007 18:56:58      ANE4953I (Session: 4492, Node: WATSON)
> Total number of
>                           objects archived:    18,205 (SESSION: 4492)
> 11/05/2007 18:56:58      ANE4958I (Session: 4492, Node: WATSON)
> Total number of
>                           objects updated:          0 (SESSION: 4492)
> 11/05/2007 18:56:58      ANE4960I (Session: 4492, Node: WATSON)
> Total number of
>                           objects rebound:          0 (SESSION: 4492)
> 11/05/2007 18:56:58      ANE4957I (Session: 4492, Node: WATSON)
> Total number of
>                           objects deleted:          0 (SESSION: 4492)
> 11/05/2007 18:56:58      ANE4970I (Session: 4492, Node: WATSON)
> Total number of
>                           objects expired:          0 (SESSION: 4492)
> 11/05/2007 18:56:58      ANE4959I (Session: 4492, Node: WATSON)
> Total number of
>                           objects failed:          34 (SESSION: 4492)
> 11/05/2007 18:56:58      ANE4961I (Session: 4492, Node: WATSON)
> Total number of
>                           bytes transferred: 218.07 GB (SESSION: 4492)
> 11/05/2007 18:56:58      ANE4963I (Session: 4492, Node: WATSON)
> Data transfer
>                           time:                6,507.48 sec
> (SESSION: 4492)
> 11/05/2007 18:56:58      ANE4966I (Session: 4492, Node: WATSON)
> Network data
>                           transfer rate:        35,138.79 KB/sec
> (SESSION: 4492)
> 11/05/2007 18:56:58      ANE4967I (Session: 4492, Node: WATSON)
> Aggregate data
>                           transfer rate:      17,066.03 KB/sec
> (SESSION: 4492)
> 11/05/2007 18:56:58      ANE4968I (Session: 4492, Node: WATSON)
> Objects compressed
>                           by:                    0% (SESSION: 4492)
> 11/05/2007 18:56:58      ANE4964I (Session: 4492, Node: WATSON)
> Elapsed processing
>                           time:            03:43:18 (SESSION: 4492)
> 11/05/2007 19:12:12      ANR0482W Session 4492 for node WATSON
> (Linux86) terminated
>                           - idle for more than 15 minutes. (SESSION:
> 4492)
> 11/05/2007 19:54:53      ANR8325I Dismounting volume TAR013L2 - 60
> minute mount
>                           retention expired.

Why would an archive (or any?) operation throw a out-of-space error?
And why would it happen about 80GB past the end of the archive pool
space, which is even weirder.  I could understand it throwing an error
at exactly 123GB.

Relevant versions: server is 5.3.4 Linux x86-64, client is 5.2.4 Linux
i386.

--Jim

<Prev in Thread] Current Thread [Next in Thread>