[I'd appreciate a copy of your replies to my personal e-mail address since I'm
not subscribed to this group. I will post a summary should I receive enough
response.]
Hi there,
I think I might have found a bug with respect to using the NDBM database
format for the "infofile" database. I'm running Amanda-2.4.2p2 under Solaris 7
(SunOS 5.7.)
First this is how I configured Amanda:
CFLAGS="-O2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64" \
LDFLAGS="-s -L/opt/GNU/lib" ./configure --prefix=/opt/amanda \
--sysconfdir=/etc/amanda --localstatedir=/var/lib/amanda \
--with-configdir=/etc/amanda --libexecdir=/opt/amanda/bin --with-user=amanda \
--with-group=bin --with-gnutar=/opt/GNU/bin/tar --with-smbclient=\
/opt/samba/bin/smbclient --with-gnutar-listdir=/var/lib/amanda/gnutar-lists \
--with-db=ndbm --with-debugging --with-gnu-ld --with-includes=/opt/GNU/include
\
--with-libraries=/opt/GNU/lib
Then there's a copy of my config file:
org "Amanda-Backup WZL-NC Sun Cluster, DailySet1"
mailto "amanda" # space separated list of operators at your site
dumpuser "amanda" # the user to run dumps under
inparallel 4 # maximum dumpers that will run in parallel (max 63)
# this maximum can be increased at compile-time,
# modifying MAX_DUMPERS in server-src/driverio.h
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
# (4 weeks * 5 amdump runs per week -- just weekdays)
tapecycle 25 tapes # the number of tapes in rotation
# 4 weeks (dumpcycle) times 5 tapes per week (just
# the weekdays) plus a few to handle errors that
# need amflush and so we do not overwrite the full
# backups performed at the beginning of the previous
# cycle
bumpsize 20 Mb # 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.
#etimeout -600 # total number of seconds for estimates.
# a positive number will be multiplied by the number of filesystems on
# each host; a negative number will be taken as an absolute total time-out.
# The default is 5 minutes per filesystem.
dtimeout 1800 # number of idle seconds before a dump is aborted.
ctimeout 30 # maximum number of seconds that amcheck waits
# for each client host
tapebufs 20
runtapes 1 # number of tapes to be used in a single run of amdump
tapedev "/dev/rmt/0bn" # the no-rewind tape device to be used
tapetype slr50 # what kind of tape it is (see tapetypes below)
labelstr "^DailySet1[0-9][0-9]*$" # label constraint regex: all tapes
must match
holdingdisk hd1 {
comment "main holding disk"
directory "/var/lib/amanda/holdingdisk" # where the holding disk is
use 1 Gb # how much space can we use on it
# a non-positive value means:
# use all space but that value
chunksize 1Gb # size of chunk if you want big dump to be
# dumped on multiple files on holding disks
# N Kb/Mb/Gb split images in chunks of size N
# The maximum value should be
# (MAX_FILE_SIZE - 1Mb)
# 0 same as INT_MAX bytes
}
infofile "/var/lib/amanda/DailySet1/curinfo" # database DIRECTORY
logdir "/var/lib/amanda/DailySet1" # log directory
indexdir "/var/lib/amanda/DailySet1/index" # index directory
tapelist "/var/lib/amanda/DailySet1/tapelist" # list of used tapes
# From "Nicki Messerschmidt"
define tapetype slr50 {
comment "just produced by tapetype program"
length 23104 mbytes
filemark 0 kbytes
speed 1784 kps
}
Now, this is what I get in the logfile:
FATAL driver infofile update failed (aida,c0t1d0s7)
This is what the "amanda" user gets via e-mail:
FAILURE AND STRANGE DUMP SUMMARY:
driver: FATAL infofile update failed (aida,c0t1d0s7)
I'm pretty sure it's NOT a permission problem:
/var/lib/amanda/:
total 8
drwxr-xr-x 4 amanda other 512 Oct 19 10:15 ./
drwxr-xr-x 3 root other 512 Oct 19 09:12 ../
drwxr-xr-x 4 amanda other 512 Oct 20 06:49 DailySet1/
drwxr-xr-x 3 amanda other 512 Oct 19 17:00 holdingdisk/
/var/lib/amanda/DailySet1:
total 28
drwxr-xr-x 4 amanda other 512 Oct 20 06:49 ./
drwxr-xr-x 4 amanda other 512 Oct 19 10:15 ../
-rw------- 1 amanda other 5754 Oct 20 06:49 amdump.1
-rw------- 1 amanda other 0 Oct 19 17:00 curinfo.dir
-rw------- 1 amanda other 0 Oct 19 17:00 curinfo.pag
drwxr-sr-x 3 amanda other 512 Oct 19 17:00 index/
-rw------- 1 amanda other 557 Oct 20 06:49 log.20011019.0
drwx------ 2 amanda other 512 Oct 20 06:49 oldlog/
-rw------- 1 amanda other 127 Oct 19 17:00 tapelist
-rw------- 1 amanda other 100 Oct 19 16:45 tapelist.amlabel
-rw------- 1 amanda other 120 Oct 19 16:49 tapelist.yesterday
/var/lib/amanda/DailySet1/index:
total 6
drwxr-sr-x 3 amanda other 512 Oct 19 17:00 ./
drwxr-xr-x 4 amanda other 512 Oct 20 06:49 ../
drwxr-sr-x 3 amanda other 512 Oct 19 17:00 aida/
/var/lib/amanda/DailySet1/index/aida:
total 6
drwxr-sr-x 3 amanda other 512 Oct 19 17:00 ./
drwxr-sr-x 3 amanda other 512 Oct 19 17:00 ../
drwxr-sr-x 2 amanda other 512 Oct 20 06:49 c0t1d0s7/
/var/lib/amanda/DailySet1/index/aida/c0t1d0s7:
total 1780
drwxr-sr-x 2 amanda other 512 Oct 20 06:49 ./
drwxr-sr-x 3 amanda other 512 Oct 19 17:00 ../
-rw------- 1 amanda other 900015 Oct 20 06:49 20011019_0.gz
/var/lib/amanda/DailySet1/oldlog:
total 4
drwx------ 2 amanda other 512 Oct 20 06:49 ./
drwxr-xr-x 4 amanda other 512 Oct 20 06:49 ../
/var/lib/amanda/holdingdisk:
total 6
drwxr-xr-x 3 amanda other 512 Oct 19 17:00 ./
drwxr-xr-x 4 amanda other 512 Oct 19 10:15 ../
drwx------ 2 amanda other 512 Oct 19 17:00 20011019/
/var/lib/amanda/holdingdisk/20011019:
total 4
drwx------ 2 amanda other 512 Oct 19 17:00 ./
drwxr-xr-x 3 amanda other 512 Oct 19 17:00 ../
As you can see all files belong to the "amanda" user and are readable and
writable by "amanda."
Any idea? Or have I found a bug in Amanda? I think I read something to the
extent that "NDBM" is not supported anymore? Why? Isn't using NDBM files much
more effective than using pure text files?
Thanks,
Ralf
--
Verkaufe Original-BMW-Raeder: L I N U X .~.
http://adsl-bergs.rz.rwth-aachen.de/~rabe The Choice /V\
of a GNU /( )\
Generation ^^-^^
