On Mon, Mar 14, 2005 at 01:59:13PM -0000, Mark Lidstone wrote:
> Hi all,
> 
> I've had a search through the FAQ, generally on the 'net and through the
> list archives, but I can't seem to find anyone else reporting similar
> symptoms to me, so here I go with my first post to the list.  If I've
> made a mistake, please be gentle...
> 
> I have a Linux box at another site.  It's running Amanda 2.4.4p2 and is
> plugged into a Compaq DDS4 drive.
> 
> Partway through a full nightly backup I'm getting the following email
> back:
> 
> > These dumps were to tape Haslar12.
> > *** A TAPE ERROR OCCURRED: [[writing file: No space left on device]]. 
> > Some dumps may have been left in the holding disk. Run amflush to 
> > flush them to tape. The next tape Amanda expects to use is: Haslar14.
> >
> > FAILURE AND STRANGE DUMP SUMMARY:
> >   olympic    /samba/company lev 0 FAILED [out of tape]
> >   olympic    /samba/company lev 0 FAILED ["data write: Connection
> reset by
> peer"]
> >   olympic    /samba/company lev 0 FAILED [dump to tape failed]
> >
> >
> > STATISTICS:
> >                           Total       Full      Daily
> >                         --------   --------   --------
> > Estimate Time (hrs:min)    0:00
> > Run Time (hrs:min)         5:07
> > Dump Time (hrs:min)        1:10       1:10       0:00
> > Output Size (meg)        5208.7     5208.7        0.0
> > Original Size (meg)      8918.1     8918.1        0.0
> > Avg Compressed Size (%)    58.4       58.4        -- 
> > Filesystems Dumped            4          4          0
> > Avg Dump Rate (k/s)      1272.8     1272.8        -- 
> >
> > Tape Time (hrs:min)        1:10       1:10       0:00
> > Tape Size (meg)          5208.7     5208.7        0.0
> > Tape Used (%)              27.0       27.0        0.0
> > Filesystems Taped             4          4          0
> > Avg Tp Write Rate (k/s)  1274.0     1274.0        -- 
> >
> > USAGE BY TAPE:
> >   Label          Time      Size      %    Nb
> >   Haslar12       1:10    5208.7   27.0     4
> >
> >
> > FAILED AND STRANGE DUMP DETAILS:
> >
> > /-- olympic    /samba/company lev 0 FAILED ["data write: Connection
> reset
> by peer"]
> > sendbackup: start [olympic:/samba/company level 0]
> > sendbackup: info BACKUP=/bin/tar
> > sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc |/bin/tar -f... -
> > sendbackup: info COMPRESS_SUFFIX=.gz
> > sendbackup: info end
> > \--------
> >
> >
> > NOTES:
> >   taper: tape Haslar12 kb 16875296 fm 5 writing file: No space left on
> device
> >
> >
> > DUMP SUMMARY:
> >                                      DUMPER STATS            TAPER
> STATS
> > HOSTNAME     DISK        L ORIG-KB OUT-KB COMP% MMM:SS  KB/s MMM:SS
> KB/s
> > -------------------------- ---------------------------------
> ------------
> > olympic      /etc/       0   35090  10956  31.2   0:22 507.0
> 0:052276.1
> > olympic      /home       0 90793005319769  58.6  69:241277.4
> 69:251277.4
> > olympic      -ba/company 0 FAILED
> ---------------------------------------
> > olympic      -a/netlogon 0      10      1  10.0   0:00   0.0   0:13
> 0.1
> > olympic      /var/log    0   17730   2938  16.6   0:04 702.6   0:04
> 786.5
> >
> > (brought to you by Amanda version 2.4.4p2)
> 
> Now, if I'm reading this right, it's saying that it's hit the end of a
> 20Gb tape at around the 5Gb mark.  Here's what I think are the relevant
> parts of my amanda.conf:
> 
> tapetype HP-DDS-4
> 
> define tapetype HP-DDS-4 {
>       comment "just produced by tapetype prog (hardware compression
> on)"
>       length 17021 mbytes
>       filemark 403 kbytes
>       speed 1578 kps
> }
> 
> (Some of you may recognise this - provided by rnaydenov on the Amanda
> site).
> 
> I'm wondering about a faulty tape drive or tapes?
> 

Wrong reading.  It successfully wrote about 5GB.
It failed at about 16.9GB.

> >   taper: tape Haslar12 kb 16875296 fm 5 writing file: No space left on
                           ^^^^^^^^^^^

Now, this is a 20GB tape, so even that is a bit early.
That number though does pretty well match your tapetype length.
I'd guess you are running gzip compression (output size < orig size)
and you have hardware compression turned on.  The dds compression
algorithm increases the size of already compressed, or other nearly
random data, and reduces tape capacity by 10-20%.

-- 
Jon H. LaBadie                  jon AT jgcomp DOT com
 JG Computing
 4455 Province Line Road        (609) 252-0159
 Princeton, NJ  08540-4322      (609) 683-7220 (fax)