Results 1 to 2 of 2

Thread: tape stats wrong?

  1. #1

    Default tape stats wrong?

    amstatus MonthlySet1 gives the following output:

    taped : 0 0k 0k ( 0.00%) ( 0.00%)
    tape 1 : 0 1958710080k 1958710080k (495.48%) MonthlySet1-8 (934 chunks)



    Does that mean it has written 1.9TB on a 400GB LTO-3 tape?

    The files are highly compressible - however, compression is disabled in my dump type:

    compress none
    program "GNUTAR"
    strategy standard
    priority high
    auth "bsd"
    dumpcycle 0
    tape_splitsize 40 Gb
    fallback_splitsize 2 Gb

  2. #2

    Default

    I believe that hardware compression is also disabled. Here is the sequence of events in my setup:

    amtapetype
    - hardware compression warning is displayed
    mt-st /dev/st0 compression off
    amtapetype
    - stats suggest that hardware compression is now disabled

    amdump MonthlySet1

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •