Tape spanning and `amadmin info`

I've begun using the new tape spanning feature of amanda 2.4.5 and it seems to 
work quite well.   It came along just in time, as I have a DLE that just 
recently became larger than a single tape.

My question is this:  I know that full backups of this large DLE are now split 
over two tapes.  But when I run 'amadmin CONFIG info' it shows:

Current info for client.lbl.gov /home/datastore_REST:
  Stats: dump rates (kps), Full:  16520.0, 16145.0, 13455.0
                    Incremental:  3147.0, 2063.0, 1870.0
          compressed size, Full: -100.0%,-100.0%,-100.0%
                    Incremental: -100.0%,-100.0%,-100.0%
  Dumps: lev datestmp  tape             file   origK   compK secs
          0  20060509  PhysicsSet101       5 157707590 157707590 9546
          1  20060510  PhysicsSet123      24  883060  883060  428
          2  20060511  PhysicsSet113      29  607500  607500  193


The level 0 dump is reported as residing on tape PhysicsSet101.  In fact, only 
PART of the level 0 dump is on that tape, and the other tape holding the rest 
of the chunks is not mentioned.


Periodically I pull a set of tapes from my changer to be set aside for 
archival purposes.   In the past I have relied on `amadmin info` to tell me 
what tapes would need to be pulled to have a full dumpcycle.  Now it seems, 
with tape spanning, this information is not quite accurate.

I'm not quite sure what the solution is, since this is a new condition for 
amanda (a single DLE dump not residing on a single tape).

-- 
--------------------------------------------------------------
Jeffrey Anderson                        | jdanderson AT lbl DOT gov
Lawrence Berkeley National Laboratory   | 
Office: 50A-5104E                       | Mailstop 50A-5101
Phone: 510 486-4208                     | Fax: 510 486-6808