Amanda-Users

Out of space problem

2008-05-05 21:17:42
Subject: Out of space problem
From: Nigel Allen <dna AT edrs.com DOT au>
To: amanda-users AT amanda DOT org
Date: Tue, 06 May 2008 10:30:55 +1000
Hi All

I'm experiencing an odd problem with a USB DAT drive that keeps running out of space. Apologies for the length of the post.

The drive is supposed to be 36 / 72 GB.

Here's the kind of thing I see when I run a level 0 dump.

These dumps were to tape DailySet1-18.
*** A TAPE ERROR OCCURRED: [No more writable valid tape found].
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: DailySet1-19.

FAILURE AND STRANGE DUMP SUMMARY:
  mail.XXXXXXXX.com.au  mapper/VolGroup00-LogVol00  lev 0  FAILED [out of tape]


STATISTICS:
                          Total       Full      Incr.
                        --------   --------   --------
Estimate Time (hrs:min)    0:04
Run Time (hrs:min)        14:44
Dump Time (hrs:min)       11:22      11:22       0:00
Output Size (meg)       33927.1    33927.1        0.0
Original Size (meg)     50710.1    50710.0        0.0
Avg Compressed Size (%)    66.9       66.9       10.0   (level:#disks ...)
Filesystems Dumped            2          1          1   (1:1)
Avg Dump Rate (k/s)       849.1      849.1        8.5

Tape Time (hrs:min)        0:00       0:00       0:00
Tape Size (meg)             0.0        0.0        0.0
Tape Used (%)               0.0        0.0        0.0   (level:#disks ...)
Filesystems Taped             1          0          1   (1:1)

Chunks Taped                  0          0          0
Avg Tp Write Rate (k/s)     7.4        --         7.4

USAGE BY TAPE:
  Label              Time      Size      %    Nb    Nc
  DailySet1-18       0:00       32K    0.0     1     0
NOTES:
  planner: Forcing full dump of mail.XXXXXXXX.com.au:mapper/VolGroup00-LogVol00 
as directed.
  taper: tape DailySet1-18 kb 31022240 fm 2 writing file: No space left on 
device
  driver: Taper  error: "[writing file: No space left on device]"
  driver: going into degraded mode because of taper component error.
  big estimate: mail.XXXXXXXX.com.au sda1 1
                est: 64K    out 32K

Here is the amanda.conf file with everything not used snipped out:

org "DailySet1"         # your organization name for reports
mailto "amandabackup"   # space separated list of operators at your site
dumpuser "amandabackup" # the user to run dumps under
inparallel 4 # maximum dumpers that will run in parallel (max 63)
dumporder "sssS"        # specify the priority order of each dumper
taperalgo first # The algorithm used to choose which dump image to send
displayunit "k"         # Possible values: "k|m|g|t"
netusage  600 Kbps      # maximum net bandwidth for Amanda, in KB per sec
dumpcycle 4 weeks       # the number of days in the normal dump cycle
runspercycle 20         # the number of amdump runs in dumpcycle days
tapecycle 21 tapes      # the number of tapes in rotation
bumpsize 20 Mb          # minimum savings (threshold) to bump level 1 -> 2
bumppercent 20          # minimum savings (threshold) to bump level 1 -> 2
bumpdays 1              # minimum days at each level
bumpmult 4              # threshold = bumpsize * bumpmult^(level-1)
etimeout 300            # number of seconds per filesystem for estimates.
dtimeout 1800           # number of idle seconds before a dump is aborted.
ctimeout 30             # maximum number of seconds that amcheck waits
tapebufs 20
runtapes 1 # number of tapes to be used in a single run of amdump
tapedev "/dev/nst0"     # the no-rewind tape device to be used
changerfile "/etc/amanda/DailySet1/changer.conf"
changerdev "/dev/null"
maxdumpsize -1 # Maximum number of bytes the planner will schedule tapetype HP-DAT72 # what kind of tape it is (see tapetypes below) labelstr "^DailySet1-[0-9][0-9]*$" # label constraint regex: all tapes must match
amrecover_do_fsf yes            # amrecover will call amrestore with the
amrecover_check_label yes       # amrecover will call amrestore with the
amrecover_changer "null:" # amrecover will use the changer if you restore
holdingdisk hd1 {
    comment "main holding disk"
    directory "/dumps/amanda"   # where the holding disk is
    use -10  Gb         # how much space can we use on it
    chunksize 1Gb       # size of chunk if you want big dump to be
    }
autoflush no #
infofile "/etc/amanda/DailySet1/curinfo"        # database DIRECTORY
logdir   "/etc/amanda/DailySet1"                # log directory
indexdir "/etc/amanda/DailySet1/index"  # index directory

define tapetype HP-DAT72 {
    comment "HP DAT72 USB with hardware compression on"
    length 72 G
}

define dumptype global {
    comment "Global definitions"
}

define dumptype custom-compress {
   global
   program "GNUTAR"
   comment "Dump with custom client compression"
   exclude list "/etc/amanda/exclude.gtar"
   compress client custom
   client_custom_compress "/usr/bin/bzip2"
}

define interface local {
    comment "a local disk"
    use 1000 kbps
}
define interface le0 {
    comment "10 Mbps ethernet"
    use 400 kbps
}

and finally the disklist:

mail.airsolutions.com.au mapper/VolGroup00-LogVol00 custom-compress
mail.airsolutions.com.au        sda1    custom-compress

Any idea where I can start would be appreciated (apart from "bigger tape" or "less data").

Rgds

Nigel.




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