Is this OK? Ignoring cruft file
Hi all,
I added a 'big' disk to my disklist yesterday. About 8G.
Flushing the files from the holding disk results in
NOTES:
amflush: beosrv-1._redhat.0.2: ignoring cruft file.
amflush: beosrv-1._redhat.0.3: ignoring cruft file.
taper: tape xic03 kb 13511296 fm 58 [OK]
Should I worry about this? Did only 2G of the backup actually make it to the tape?
The holding disk is empty after this, and it seems to happen only when a disk
is freshly added to the disklist. If it is due for a full backup lateron, there is no
such message.
I've set the chunksize of my holding disk to 2G.
I have to run amdump and amflush in separate runs. This is working fine.
I verify every tape written and that only gave errors once when the tape
was exhausted and completed on the next tape (expected error).
Thanks for any info!
Regards,
Edwin Hakkennes
--
From: Amanda user[SMTP:[EMAIL PROTECTED]]
Reply To: Admins
Sent: Thursday, August 15, 2002 10:45 AM
To: Multiple recipients of list admins
Subject:xic AMFLUSH MAIL REPORT FOR August 15, 2002
The dumps were flushed to tape xic03.
The next 2 tapes Amanda expects to used are: xic04, xic05.
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 2:30
Dump Time (hrs:min)0:00 0:00 0:00
Output Size (meg) 0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Tape Time (hrs:min)2:29 2:19 0:10
Tape Size (meg) 13194.612526.2 668.5
Tape Used (%) 62.7 59.53.2 (level:#disks ...)
Filesystems Taped58 29 29 (1:29)
Avg Tp Write Rate (k/s) 1506.3 1535.8 1107.9
NOTES:
amflush: beosrv-1._redhat.0.2: ignoring cruft file.
amflush: beosrv-1._redhat.0.3: ignoring cruft file.
taper: tape xic03 kb 13511296 fm 58 [OK]
DUMP SUMMARY:
DUMPER STATS
TAPER STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s
MMM:SS KB/s
--- --
beosrv-1 /0 645860 310720 48.1 N/A N/A
5:54 878.7
beosrv-1 /install NO FILE TO FLUSH
--
beosrv-1 /redhat 0 7980690 7649568 95.9 N/A N/A
66:081927.9
beosrv-1 /srv/apps1 143901056 7.3 N/A N/A
0:09 117.0
beosrv-1 /srv/data12030 256 12.6 N/A N/A
0:09 28.9
beosrv-1 /srv/libs1 14140 416 2.9 N/A N/A
0:12 34.2
beosrv-1 /srv/projects0 83650 63456 75.9 N/A N/A
0:411549.7
beosrv-1 /srv/scratch 0 10 64 640.0 N/A N/A
0:05 13.3
beosrv-1 /srv/users 0 4 22848 57.1 N/A N/A
0:211105.3
beosrv-1 /srv/xic 0 10 64 640.0 N/A N/A
0:11 6.1
beosrv-1 /var 1 391203872 9.9 N/A N/A
0:11 343.3
beosrv-2 /0 268150 121376 45.3 N/A N/A
2:38 768.0
beosrv-2 /var 0 107840 59520 55.2 N/A N/A
0:431372.2
dilbert /1 780 160 20.5 N/A N/A
0:10 16.5
dilbert /boot1 10 64 640.0 N/A N/A
0:10 6.2
dilbert /home1 340001472 4.3 N/A N/A
0:09 162.7
dilbert /usr 1 101601056 10.4 N/A N/A
0:09 117.4
dilbert /usr/local 1 270 64 23.7 N/A N/A
0:05 13.0
dilbert /var 1 239906752 28.1 N/A N/A
0:17 399.2
jansen_en_janssen/.kde1 10 64 640.0 N/A N/A
0:09 7.2
jansen_en_janssen/.kde2 1 20 64 320.0 N/A N/A
0:09 7.4
jansen_en_janssen/bin 1 10 64 640.0 N/A N/A
0:09 7.2
jansen_en_janssen/boot088307968 90.2 N/A N/A
0:13 616.1
jansen_en_janssen/dev 1 70 64 91.4 N/A N/A
0:09 7.2
jansen_en_janssen/etc 081301792 22.0 N/A N/A
0:09 194.8
Gizli cekim
Hic bir yerde bulup izleyemeyeceginiz icerigi size http://www.2seks.com sunuyor. TURK VE AVRUPALI AMATOR KIZLAR BULGAR KIZLARI ROMEN HATUNLAR TURK TECAVUZ FILMLERI KIZLAR YURDU ALMANYA'NIN SAPIK HATUNLARI OTELDEKI GIZLI KAMERALAR VE DAHASI... Hepsi orjinal ve kaliteli kayitlar. Hemen giris yapin ve tadini cikartin http://www.2seks.com
Re: failure strange dump
Hi thanks for your email, I'm sorry to be a pain but could you tell me if I can just add the amanda user to my root group. If not what permission does the new disk group need? Thanks for all your help so far. Jane. On Wednesday 14 August 2002 09:54, you wrote: Thanks for your email, if I want to change my amanda to run as a different user does this mean I have to re-install it? Jane. Uhh, what source did you use to first do it? The reason I ask is that there are rpms floating about, usually of a somewhat aged nature. amanda is a work in progress although nothing has been done that makes for version incompatibilities since 2.4.1 was released 2 or so years ago. I am personally running the latest snapshot of version 2.4.3b3 which is available as tarballs from the web site of a Mr. Martineau at http://www.iro.umontreal.ca/~martinea/amanda This is unpacked as user root in the /home/amanda directory, and a chown -R amanda:disk amanda-2.4.3b3-20020805 is then done. Then I grab my configure script from the previous build and copy it into this newly unpacked directory. This script looks like this: - #!/bin/sh make clean rm -f config.status config.cache ./configure --with-user=amanda \ --with-group=disk \ --with-owner=amanda \ --with-tape-device=/dev/nst0 \ --with-changer-device=/dev/sg1 \ --with-gnu-ld \ --prefix=/usr/local \ --with-debugging=/tmp/amanda-dbg/ \ --with-tape-server=192.168.1.3 \ --with-amandahosts \ --with-configdir=/usr/local/etc/amanda --- You'll need to modify the obvious stuff above of course, but once this script has been used, it should be used for all subsequent rebuilds. Do a chmod +x on whatever you name this and it will run directly, or you can do a sh ./scriptname also. But first su yourself to be user amanda before running it. When thats done, make it. When thats done, exit back to root, and make install This will automaticly take care of all the various permissions bits for you, and amanda will then be run from the user amanda's crontab or by the user amanda if by hand. You will of course need to generate the user amanda and make amanda a member of the group disk. Such utilities as linuxconf make that an easy job. Last, your email agent is, in the spam filer 'Declude's eyes, (my ISP uses that utility for spam and viri killing) a broken one which caused my ISP to add a marker header, which in turn caused your message to be marked as read and moved to the local Junquemail folder for later forwarding to [EMAIL PROTECTED] I normally give it a quick scan before doing so and caught this one before I killed it. So you might want to see if its miss-configured or whatever. On Wednesday 14 August 2002 04:14, janebackup wrote: Hi Chris, Thanks for your reply, I don't use the email facility but I run a amreport and I get the following: FAILURE STRANGE DUMP dataserv / Results missing Amanda is running as root so I don't think its permissions. amanda doesn't like running as root, usually totally refusing to, but will get root perms when she needs to. amanda should be run as an unpriviledged user who is a member of group disk or maybe backup, and will do an suid when required. I'm compiling from source. I would be grateful if somebody could help me! The contents of this list usually get a recipe for building amanda from me about weekly, so you might want to look at the last couple of weeks worth to see one way of doing it that works here. Thanks in advance and for your help so far. Jane. jane, the disklist file looks fine. are you getting an email with errors? if so please send that and I can maybe help. If your getting disk offline errors it may be a permission issue. what user is amanda running as? are the filesystems (/dev/[sh]da[0-9]) owned by the group that amanda is running as? These are the first two things I would check. btw: I've had problems editing the group file by hand and adding amanda user to a group. It seems that the default group must be correct and amanda must be compiled with the correct options. Are you compiling from source or using an rpm? chrisj janebackup wrote: Chris, Thanks for your reply, yes I was trying to backup a single directory (thought I'd do this first just to test). If I have to backup the filesystem does this mean if I put the following entry in my disklist file?: dataserv/ always-full Cus I've already tried this and I still get the same errors. Is my disklist file wrong? Thanks for your help. Jane. jane Are you trying to backup a filesystem or a directory. Amanda is made to dump filesystems at the disk level and won't do
Re: Is this OK? Ignoring cruft file
On Thu, Aug 15, 2002 at 11:47:24AM +0200, Edwin Hakkennes wrote: Hi all, I added a 'big' disk to my disklist yesterday. About 8G. Flushing the files from the holding disk results in NOTES: amflush: beosrv-1._redhat.0.2: ignoring cruft file. amflush: beosrv-1._redhat.0.3: ignoring cruft file. taper: tape xic03 kb 13511296 fm 58 [OK] Should I worry about this? Did only 2G of the backup actually make it to the tape? The holding disk is empty after this, and it seems to happen only when a disk is freshly added to the disklist. Why do you think only 2GB? Your chunksize? The above report says kb 13511296, i.e. 13.5GB. It also says fm 58, i.e. 58 file marks, about 56 disklist entries. If it is due for a full backup lateron, there is no such message. Don't know what message you might expect, but try amadmin xic due beosrv-1 /redhat to check when the next full dump is due. I don't know all the reason for cruft files, but occasionally I've seen empty directories or files that an amflush cleans up and reports as cruft. I've set the chunksize of my holding disk to 2G. If your file system has a 2GB file size limit, I believe the recommendation is to have the chucksize below, not at the limit. If it handles larger files, then 2GB is fine. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: failure strange dump
On Thu, Aug 15, 2002 at 02:40:33PM +0100, janebackup wrote: Hi thanks for your email, I'm sorry to be a pain but could you tell me if I can just add the amanda user to my root group. If not what permission does the new disk group need? YMMV, this is my system. $ ls -lL /dev/dsk total 0 ... brw-r- 1 root sys 29,392 Jul 20 2001 c1t6d0s8 brw-r- 1 root sys 29,393 Jul 20 2001 c1t6d0s9 ^ ^^^ group read amanda must have this group permissions Seldom (in my experience) is the disk group the root group. Some systems allow only a single group membership at a time. In that case amanda should login as part of the disk group (sys for me). Other system allow multiple, simultaneous group membership. On those, amanda needs be listed as a member of the disk group (sys for me). 300 lines of email message for a 3 line question is overkill. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Is this OK? Ignoring cruft file
--On Thursday, August 15, 2002 11:47:24 +0200 Edwin Hakkennes [EMAIL PROTECTED]
wrote:
Hi all,
I added a 'big' disk to my disklist yesterday. About 8G.
Flushing the files from the holding disk results in
NOTES:
amflush: beosrv-1._redhat.0.2: ignoring cruft file.
amflush: beosrv-1._redhat.0.3: ignoring cruft file.
taper: tape xic03 kb 13511296 fm 58 [OK]
Should I worry about this? Did only 2G of the backup actually make it to the tape?
It wrote 13.5G to tape, and according to your output below, 7.6G of that was from
your beosrv-1 /redhat disklist entry. I think the cruft file messages are just
a result of the somewhat asynchronous nature of amanda. The chunk files are removed
after each set is written to tape but may not be all gone yet when Amanda scans
for other chunk sets to flush to tape. Anything that it doesn't know what to do
with is reported as 'cruft', whether it is some odd file put in the holding disk
or a chunk that isn't part of a complete set (the chunk files are named as
host.filesystem.level.chunknumber).
'Notes' are just informative, 'strange' needs to be examined, it may or may not
be a problem, and 'warning' you better pay attention to.
Frank
The holding disk is empty after this, and it seems to happen only when a disk
is freshly added to the disklist. If it is due for a full backup lateron, there is no
such message.
I've set the chunksize of my holding disk to 2G.
I have to run amdump and amflush in separate runs. This is working fine.
I verify every tape written and that only gave errors once when the tape
was exhausted and completed on the next tape (expected error).
Thanks for any info!
Regards,
Edwin Hakkennes
--
From: Amanda user[SMTP:[EMAIL PROTECTED]]
Reply To: Admins
Sent: Thursday, August 15, 2002 10:45 AM
To: Multiple recipients of list admins
Subject: xic AMFLUSH MAIL REPORT FOR August 15, 2002
The dumps were flushed to tape xic03.
The next 2 tapes Amanda expects to used are: xic04, xic05.
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 2:30
Dump Time (hrs:min)0:00 0:00 0:00
Output Size (meg) 0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Tape Time (hrs:min)2:29 2:19 0:10
Tape Size (meg) 13194.612526.2 668.5
Tape Used (%) 62.7 59.53.2 (level:#disks ...)
Filesystems Taped58 29 29 (1:29)
Avg Tp Write Rate (k/s) 1506.3 1535.8 1107.9
NOTES:
amflush: beosrv-1._redhat.0.2: ignoring cruft file.
amflush: beosrv-1._redhat.0.3: ignoring cruft file.
taper: tape xic03 kb 13511296 fm 58 [OK]
DUMP SUMMARY:
DUMPER STATS
TAPER STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS
KB/s MMM:SS KB/s
---
--
beosrv-1 /0 645860 310720 48.1 N/A
N/A5:54 878.7
beosrv-1 /install NO FILE TO FLUSH
--
beosrv-1 /redhat 0 7980690 7649568 95.9 N/A
N/A 66:081927.9
beosrv-1 /srv/apps1 143901056 7.3 N/A
N/A0:09 117.0
beosrv-1 /srv/data12030 256 12.6 N/A
N/A0:09 28.9
beosrv-1 /srv/libs1 14140 416 2.9 N/A
N/A0:12 34.2
beosrv-1 /srv/projects0 83650 63456 75.9 N/A
N/A0:411549.7
beosrv-1 /srv/scratch 0 10 64 640.0 N/A
N/A0:05 13.3
beosrv-1 /srv/users 0 4 22848 57.1 N/A
N/A0:211105.3
beosrv-1 /srv/xic 0 10 64 640.0 N/A
N/A0:11 6.1
beosrv-1 /var 1 391203872 9.9 N/A
N/A0:11 343.3
beosrv-2 /0 268150 121376 45.3 N/A
N/A2:38 768.0
beosrv-2 /var 0 107840 59520 55.2 N/A
N/A0:431372.2
dilbert /1 780 160 20.5 N/A
N/A0:10 16.5
dilbert /boot1 10 64 640.0 N/A
N/A0:10 6.2
dilbert /home1 340001472 4.3 N/A
N/A0:09 162.7
dilbert
Problem - Amanda doesn't work
Hi,
we recently installed RedHat 7.3 on our Internet Server. Now we are looking for a
backup solution decided to try Amanda, which is included in the RedHat distribution.
We have installed and configured it as described but have no opinion on setting the
tapeype. We are using a DAT device from Sony with DDS2 tapes.
The output from mt status was:
SCSI 2 tape drive:
File number=0, block number=0, partition=0.
Tape block size 28672 bytes. Density code 0x13 (DDS (61000 bpi)). Soft error count
since last status=0 General status bits on (4101):
BOT ONLINE IM_REP_EN
First we tryed to label a tape with amlabel getting the output:
[root@inetsrv root]# amlabel Freitag Freitag_1
rewinding, reading label, not an amanda tape
rewinding, writing label Freitag_1
amlabel: writing label: Invalid argument
In the messages we got the output:
Aug 15 15:48:04 inetsrv kernel: st0: Write not multiple of tape block size.
So we thougt perhapes the tapetype must be set correctly, so we tried the progi
tapetype with the following output:
[root@inetsrv root]# /usr/sbin/tapetype -f /dev/nst0 -t DDS2
tapetype: could not write any data in this pass: short write
Our config file:
#
# amanda.conf
#
org Freitag
mailto root
dumpuser amanda
inparallel 4
netusage 600 Kbps
dumpcycle 1 weeks
runspercycle 1 weeks
tapecycle 4 tapes
bumpsize 20 Mb
bumpdays 1
bumpmult 4
etimeout 300
runtapes 1
tapedev /dev/nst0
tapetype Sony-DAT
labelstr ^Freitag_[0-9]*$
holdingdisk hd1 {
comment main holding disk
directory /var/tmp
use 290 Mb
}
infofile /log/amanda/Freitag/curinfo # database filename
logdir /log/amanda/Freitag # log directory
indexdir /log/amanda/Freitag/index# index directory
tapelist /log/amanda/Freitag/tapelist # list of used tapes
# tapetypes
define tapetype Sony-DAT {
comment Sony DAT tape drives
length 4000 mbytes
filemark 29 kbytes
speed 1024 kbytes
}
# dumptypes
define dumptype global {
comment Global definitions
}
define dumptype always-full {
global
comment Full dump of this filesystem always
compress none
priority high
dumpcycle 0
}
define dumptype root-tar {
global
program GNUTAR
comment root partitions dumped with tar
compress none
index
exclude list /usr/local/lib/amanda/exclude.gtar
priority low
}
define dumptype user-tar {
root-tar
comment user partitions dumped with tar
priority medium
}
define dumptype high-tar {
root-tar
comment partitions dumped with tar
priority high
}
define dumptype comp-root-tar {
root-tar
comment Root partitions with compression
compress client fast
}
define dumptype comp-user-tar {
user-tar
compress client fast
}
define dumptype holding-disk {
global
comment The master-host holding disk itself
holdingdisk no # do not use the holding disk
priority medium
}
define dumptype comp-user {
global
comment Non-root partitions on reasonably fast machines
compress client fast
priority medium
}
define dumptype nocomp-user {
comp-user
comment Non-root partitions on slow machines
compress none
}
define dumptype comp-root {
global
comment Root partitions with compression
compress client fast
priority low
}
define dumptype nocomp-root {
comp-root
comment Root partitions without compression
compress none
}
define dumptype comp-high {
global
comment very important partitions on fast machines
compress client best
priority high
}
define dumptype nocomp-high {
comp-high
comment very important partitions on slow machines
compress none
}
define dumptype nocomp-test {
global
comment test dump without compression, no /etc/dumpdates
recording
compress none
record no
priority medium
}
define dumptype comp-test {
nocomp-test
comment test dump with compression, no /etc/dumpdates recording
compress client fast
}
We really have no idea on where we should search for a fault in the configuration.
We are hardly thinking about installing W2K!
We will be glad about any help!
Re: failure strange dump
On Thursday 15 August 2002 09:40, janebackup wrote: Hi thanks for your email, I'm sorry to be a pain but could you tell me if I can just add the amanda user to my root group. If not what permission does the new disk group need? Thanks for all your help so far. Jane. I suppose so, here, 'disk' has amanda and root listed as alternate members by the linuxconf display. And, using linuxconf to edit things, its easy enough to fix either way. Your emailer is still miss-configured, so I had to rescue this from the Junquemail folder. My ISP uses the Declude spam/viri filter, and it doesn't like mail coming from localhost. I also note that a CC: was sent to the list, so I'll ignore any more of these in my personal inbox, and answer those on the list instead. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.11% setiathome rank, not too shabby for a WV hillbilly
Re: failure strange dump
On Thursday 15 August 2002 10:47, Jon LaBadie wrote: On Thu, Aug 15, 2002 at 02:40:33PM +0100, janebackup wrote: Hi thanks for your email, I'm sorry to be a pain but could you tell me if I can just add the amanda user to my root group. If not what permission does the new disk group need? YMMV, this is my system. $ ls -lL /dev/dsk total 0 ... brw-r- 1 root sys 29,392 Jul 20 2001 c1t6d0s8 brw-r- 1 root sys 29,393 Jul 20 2001 c1t6d0s9 ^ ^^^ group read amanda must have this group permissions Seldom (in my experience) is the disk group the root group. Some systems allow only a single group membership at a time. In that case amanda should login as part of the disk group (sys for me). Other system allow multiple, simultaneous group membership. On those, amanda needs be listed as a member of the disk group (sys for me). 300 lines of email message for a 3 line question is overkill. Agreed. I aso got a private copy of this, and I took her question to be 'could I make amanda a member of group root' which I said I suppose so since the group 'disk' has amanda and root as alternate members here on my machine according to linuxconf. Is this not correct, Jon? -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.11% setiathome rank, not too shabby for a WV hillbilly
Re: Is this OK? Ignoring cruft file
On Thursday 15 August 2002 11:01, Frank Smith wrote: --On Thursday, August 15, 2002 11:47:24 +0200 Edwin Hakkennes [EMAIL PROTECTED] wrote: Hi all, I added a 'big' disk to my disklist yesterday. About 8G. Flushing the files from the holding disk results in NOTES: amflush: beosrv-1._redhat.0.2: ignoring cruft file. amflush: beosrv-1._redhat.0.3: ignoring cruft file. taper: tape xic03 kb 13511296 fm 58 [OK] Should I worry about this? Did only 2G of the backup actually make it to the tape? It wrote 13.5G to tape, and according to your output below, 7.6G of that was from your beosrv-1 /redhat disklist entry. I think the cruft file messages are just a result of the somewhat asynchronous nature of amanda. The chunk files are removed after each set is written to tape but may not be all gone yet when Amanda scans for other chunk sets to flush to tape. Anything that it doesn't know what to do with is reported as 'cruft', whether it is some odd file put in the holding disk or a chunk that isn't part of a complete set (the chunk files are named as host.filesystem.level.chunknumber). 'Notes' are just informative, 'strange' needs to be examined, it may or may not be a problem, and 'warning' you better pay attention to. Frank Hummm, this brings up an interesting thought, Frank. If amanda removed the chunk files as they were written, then how would amanda go about the case of hitting EOT in the middle of the last chunk file, finding that it has perms (via runtapes=2 for instance) to use the next tape in the magazine, at which point amanda supposedly restarts that disklist entries dump from the top. If there were 4 chunk files, 3 of which had been written and deleted when this occured, it seems to me that amanda would find herself between a rock and a hard place to be able to restart that particular disklist entries dump. It certainly wouldn't be very time efficient to redo the whole entry although that does seem to be the only way to recover. So how is this scenario resolved by amanda? -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.11% setiathome rank, not too shabby for a WV hillbilly
Re: Problem - Amanda doesn't work
On Thu, Aug 15, 2002 at 05:07:22PM +0200, Marcus Kramer wrote: Hi, we recently installed RedHat 7.3 on our Internet Server. Now we are looking for a backup solution decided to try Amanda, which is included in the RedHat distribution. We have installed and configured it as described but have no opinion on setting the tapeype. We are using a DAT device from Sony with DDS2 tapes. Hard returns in long lines are appreciated by some unix mail readers. The output from mt status was: SCSI 2 tape drive: File number=0, block number=0, partition=0. Tape block size 28672 bytes. Density code 0x13 (DDS (61000 bpi)). Soft error count since last status=0 General status bits on (4101): BOT ONLINE IM_REP_EN First we tryed to label a tape with amlabel getting the output: [root@inetsrv root]# amlabel Freitag Freitag_1 rewinding, reading label, not an amanda tape rewinding, writing label Freitag_1 amlabel: writing label: Invalid argument In the messages we got the output: Aug 15 15:48:04 inetsrv kernel: st0: Write not multiple of tape block size. I'm treading on very thin ice here. Your mt status reports a block size. I've not seen this, but my guess is that is a configurable setting in either the tape device or the driver. Perhaps an mt option? Amanda uses a 32K block size. So the message Write not multiple of tape block size is quite reasonable given the reported block size of 28672 bytes. 28672? 28K? Very interesting. Anyone know why that might be the setting? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Problem - Amanda doesn't work
On Thursday 15 August 2002 11:07, Marcus Kramer wrote:
Hi,
we recently installed RedHat 7.3 on our Internet Server. Now we
are looking for a backup solution decided to try Amanda, which is
included in the RedHat distribution. We have installed and
configured it as described but have no opinion on setting the
tapeype. We are using a DAT device from Sony with DDS2 tapes.
All of this is located in the amanda.conf file, and I'd hope by now
someone has managed to edit a DDS2 tapetype into the supplied
example. If not, here is one such 'DDS2' entry which you can add
to your amanda.conf:
---
define tapetype DDS2 {
comment just produced by tapetype program
length 3780 mbytes
# lbl-templ /usr/local/etc/amanda/DailySet1/DDS2.ps
filemark 0 kbytes
speed 380 kps
}
Also, and I inadvertantly clipped that portion of your message while
clipping that out of my amanda.conf, if you will consult your
amanda.conf while adding the above file someplace in the tapetypes
entries, you will also find a label section which describes the
permissable labeling format. You can either stay within that
format, or change the format to suit your (apparently german)
native language. Do whatever you are comfortable with as long as
the label chosen fits within that editable constraint. This is
done I suspect so that one can have more than one set of tapes for
amanda's use, each 'set' with a different naming convention, and
amanda will then prevent you from in-advertantly mixing up the
tapes which is a Good Thing(tm) :-)
--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
99.11% setiathome rank, not too shabby for a WV hillbilly
Re: Problem - Amanda doesn't work
Hello Marcus. Another area to look at besides the config is the modules, lsmod to see if the right modules are loaded. Is your tape an ide type? I have a different type of set up, but its an ide and I used scsi emulation to get it to work. If this is the case with yours, this is what I did: # rmmod ide-tape # depmod ide-scsi # modprobe ide-scsi # depmod st # modprobe st Maybe I'm way off, I'm no expert, but if you give a 100 monkeys 100 camera's and enough film, you'll eventually come up with a master piece! Chow, Trevor. == One volunteer is as strong as ten hired men. ==
Update on Index Tees - Data Timeouts
Test #1: I commented out all filesystems except one of the failing ones and simply ran amdump. RESULT: Worked perfectly. Test #2: Added in the final two failing filesystems and ran amdump. RESULT: Worked perfectly. Any suggestions on what it could be. I have the following set in amanda.conf: inparallel 16 netusage 75000 Kbps tapebufs 40 reserve 25 for my holdingdisk I have set the chunksize to 1Gb Which side is most likely to cause a Data Timeout client or server? Are there any suggestions on where to do the compression? Jon, thank you for your response regarding the ufsdumps. I had reverted back to that during that particular run to see if I could ease some contention somewhere. But to no avail. Thanks again, Jim On Wed, 2002-08-14 at 14:37, Joshua Baker-LePain wrote: On 14 Aug 2002 at 2:19pm, Jim Summers wrote In an effort to debug this problem, is there a way I can interactively run the command(s) that amanda would run to see if anything is dumped to stdout? If so, are these the commands in runtar and sendbackup? Or would it be better to comment out all filesystems except one of the ones having problems and run amdump? The exact commands are in both runtar*debug and sendbackup*debug. It would be interesting to comment out some filesystems to see if it's a function of having too much going on on one host, or if it's something particular to those filesystems. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Holding Disk Question
What is the best size for a holding disk - is it a how long is a piece string or are there some optimal values. I have 2 servers I want to back up - the Amanda server 40gb RH Linux box - an WIN NT machine 16gb. TIA Kevin Passey
Re: Update on Index Tees - Data Timeouts
On Thu, Aug 15, 2002 at 11:08:51AM -0500, Jim Summers wrote: Test #1: I commented out all filesystems except one of the failing ones and simply ran amdump. RESULT: Worked perfectly. Test #2: Added in the final two failing filesystems and ran amdump. RESULT: Worked perfectly. Any suggestions on what it could be. Perhaps during the problem times all the file systems were doing level 0's and the dumps were running in parallel. This could cause high levels of activity that could cause great slow downs. Perhaps net contention. Perhaps multiple dumps from a single host and high cpu usage. Perhaps multiple dumps from a single disk drive and lots of disk head movement slowing things down. Now some are doing incrementals while others are level 0s. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
DLT8000s in a TL891 on Compaq kit running RedHat 7.3 Input/outputerror
Hi,
I've just started using Amanda, hoping/praying I can move away
from Arkeia, wish I still had ADSM. Anyway...
First a contribution, I haven't seen it anywhere else:
define tapetype DLT8000 {
comment Compaq DLT8000 (from tapetype)
length 38119 mbytes
filemark 32 kbytes
speed 2071 kps
}
Everything seems setup OK. The network connections are all working.
Two things though:
WARNING: info file /etc/amanda/Blue/curinfo/node3/_boot/info:
does not exist
WARNING: info file /etc/amanda/Blue/curinfo/node3/_/info: does
not exist
WARNING: info file /etc/amanda/Blue/curinfo/node4/_usr1/info:
does not exist
WARNING: info file /etc/amanda/Blue/curinfo/node4/_boot/info:
does not exist
.
.
.
This will probably go away when I start backing things up???
The second is that I get problems using tapes from 'slot 9' of my
10 slot library. I have a cleaning tape in the tenth. I have
two tape drives. I get:
amcheck-server: slot 9: rewinding tape: Input/output error
I got this first with amlabel. I configured amanda to use the
other drive. I cleaned both drives and tried a new tape in 'slot
9' but I still get the 'rewinding input/output' error.
I'm loathed to start backing things up while it still complains.
Any help would be much appreciated.
Owen.
Re: Holding Disk Question
I'm sure there are several things to consider here but one thing that comes to my mind is that your holding disk should be at least large enough to hold one nights worth of backups and maybe a little more. That way in the event that for some reason amanda can't dump everything to tape at least you have a copy on disk that you can flush to tape after you resolve the problem with the tape drive. Kevin Passey wrote: What is the best size for a holding disk - is it a how long is a piece string or are there some optimal values. I have 2 servers I want to back up - the Amanda server 40gb RH Linux box - an WIN NT machine 16gb. TIA Kevin Passey
Problem - Amanda does'nt work
Hi Marcus, you have to use the non rewindung tape device. This is /dev/nst0 instead of /dev/st0 which you obviously used. regards K.H. Timmesfeld -- == Dr. K.H. Timmesfeld Tel.: 06431 -4040 (Sekretariat) IDAS GmbH -40439 (Durchwahl) Holzheimer Strasse 96 Fax:-40410 D-65549 Limburg email: [EMAIL PROTECTED] privat: Im Feldchen 2 Tel. und Fax: 06431-41271 D-65549 Limburg
Re: DLT8000s in a TL891 on Compaq kit running RedHat 7.3 Input/outputerror
On Thu, 15 Aug 2002 at 5:30pm, Owen Williams wrote Everything seems setup OK. The network connections are all working. Two things though: WARNING: info file /etc/amanda/Blue/curinfo/node3/_boot/info: does not exist WARNING: info file /etc/amanda/Blue/curinfo/node3/_/info: does not exist WARNING: info file /etc/amanda/Blue/curinfo/node4/_usr1/info: does not exist WARNING: info file /etc/amanda/Blue/curinfo/node4/_boot/info: does not exist Nothing to worry about -- amanda will create them first run. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Update on Index Tees - Data Timeouts
On 15 Aug 2002 at 11:08am, Jim Summers wrote Any suggestions on what it could be. I have the following set in amanda.conf: inparallel 16 netusage 75000 Kbps tapebufs 40 reserve 25 for my holdingdisk I have set the chunksize to 1Gb Maybe you're hitting some network contention problems -- try cranking down inparallel? Are there any suggestions on where to do the compression? On the hosts that can handle it. I have a fast amanda server, and mostly fast clients. For the not fast clients, I do compression on the server. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Holding Disk Question
On Thu, 15 Aug 2002, Kevin Passey wrote: What is the best size for a holding disk - is it a how long is a piece string or are there some optimal values. It mostly a tuning thing that's up to you to decide what's best for you. That said, I prefer my setups to have as a minimum, enough to hold any single night's backup in its entirety. Then if something bad happens with the tape drive/media, the backups can run to completion spooled to the holding disk(s) and in the morning I can solve the tape problem and flush the holding disk(s) to tape then. Also, having enough to hold all of a single run allows you to take the greatest advantage of dumping parallelism, thus getting your client backups finished as quickly as possible. Further improvements on this theme are, 1) enough holding disk to hold an entire weekend's backups, and 2) enough holding disk to hold an entire insert length of your longest anticipated family vacation here. My motto: Disk is cheap, don't skimp on holding disk. -Mitch
Re: Holding Disk Question
On Thursday 15 August 2002 12:19, Kevin Passey wrote: What is the best size for a holding disk - is it a how long is a piece string or are there some optimal values. I have 2 servers I want to back up - the Amanda server 40gb RH Linux box - an WIN NT machine 16gb. Holding disk sizes are rather hard to pin down, and most of us seem to solve that problem by specifying a /path/to which puts it on a large partition, and then specify a reserve of a couple of gigs. amanda can backup to it while simultainously dumping from it, essentially useing it as a giant circular buffer with certain size limits stated pretty much up front. Those are: 1. No disklist entry should ever exceed the size of a single tape since amanda can't span to the next tape with a single operation. 2. If there are filesize limitations such as 2gigs on the server, then the chunksize will need to be sized less than that, otherwise its a never mind. 3. The reserved amount should be able to hold at least the incrementals of the whole system, a rather unpredictable value at best... I started out with about 27 gigs when I first set this machine up, but have eaten up several of those with source code, pictures from my new digital camera, and music from 'ogg'ing my cd collection, so I'm down to about 12 gigs which is still overkill on a 2 machine system with about 90 gigs worth of disk, not all of which is full of course. I *might* have 40 gigs worth of Junque or data, depending on how one defines the words. Amanda uses a 7 day dumpcycle here, with 20 tapes, and it normally fits a given nights activity onto one 4g tape. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.11% setiathome rank, not too shabby for a WV hillbilly
chg-zd-mtx output
Does anyone know what could cause this output? I am trying to debug my setup with a PowerVault 128T / Linux Redhat 7.3 bash-2.05a$ /usr/lib/amanda/chg-zd-mtx -info /usr/lib/amanda/chg-zd-mtx: [: : integer expression expected /usr/lib/amanda/chg-zd-mtx: [: -lt: unary operator expected 16 1 1 Jay
Re: Is this OK? Ignoring cruft file
--On Thursday, August 15, 2002 11:45:52 -0400 Gene Heskett [EMAIL PROTECTED] wrote: On Thursday 15 August 2002 11:01, Frank Smith wrote: --On Thursday, August 15, 2002 11:47:24 +0200 Edwin Hakkennes [EMAIL PROTECTED] wrote: Hi all, I added a 'big' disk to my disklist yesterday. About 8G. Flushing the files from the holding disk results in NOTES: amflush: beosrv-1._redhat.0.2: ignoring cruft file. amflush: beosrv-1._redhat.0.3: ignoring cruft file. taper: tape xic03 kb 13511296 fm 58 [OK] Should I worry about this? Did only 2G of the backup actually make it to the tape? It wrote 13.5G to tape, and according to your output below, 7.6G of that was from your beosrv-1 /redhat disklist entry. I think the cruft file messages are just a result of the somewhat asynchronous nature of amanda. The chunk files are removed after each set is written to tape but may not be all gone yet when Amanda scans for other chunk sets to flush to tape. Anything that it doesn't know what to do with is reported as 'cruft', whether it is some odd file put in the holding disk or a chunk that isn't part of a complete set (the chunk files are named as host.filesystem.level.chunknumber). 'Notes' are just informative, 'strange' needs to be examined, it may or may not be a problem, and 'warning' you better pay attention to. Frank Hummm, this brings up an interesting thought, Frank. If amanda removed the chunk files as they were written, then how would amanda go about the case of hitting EOT in the middle of the last chunk file, finding that it has perms (via runtapes=2 for instance) to use the next tape in the magazine, at which point amanda supposedly restarts that disklist entries dump from the top. If there were 4 chunk files, 3 of which had been written and deleted when this occured, it seems to me that amanda would find herself between a rock and a hard place to be able to restart that particular disklist entries dump. It certainly wouldn't be very time efficient to redo the whole entry although that does seem to be the only way to recover. So how is this scenario resolved by amanda? I said that the chunks were removed after the set was written. I haven't looked at that part of the code, just observed my holding disk in various situations, so I may not be completely correct. It appears that after all of the set of chunks belonging to a single disklist entry are successfully flushed to tape, those chunks are deleted from the disk. If a tape error occurs anytime during the flush of a set of chunks all of that set remains on disk so a subsequent amflush can start over with the first chunk of the set. I believe Edwin's 'notes' was the result of Amanda successfully flushing all of the chunks of his 'redhat' directory, but after taper returned ok a command was given to remove those chunks while amflush went ahead and rescanned the holding disk looking for anything else that needed to be flushed. Since it can take a second or two to remove large files, a couple of the chunks were still there when the scan occurred, but since the first chunk was already gone Amanda saw the other two as cruft. Of course, when Edwin looked at the disk later it was all gone by then. Frank -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.11% setiathome rank, not too shabby for a WV hillbilly -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Holding Disk Question
On Thu, Aug 15, 2002 at 10:35:18AM -0600, Scott Sanders wrote: I'm sure there are several things to consider here but one thing that comes to my mind is that your holding disk should be at least large enough to hold one nights worth of backups and maybe a little more. That way in the event that for some reason amanda can't dump everything to tape at least you have a copy on disk that you can flush to tape after you resolve the problem with the tape drive. Kevin Passey wrote: What is the best size for a holding disk - is it a how long is a piece string or are there some optimal values. I have 2 servers I want to back up - the Amanda server 40gb RH Linux box - an WIN NT machine 16gb. Ditto's on Scott's comments plus with reserve set low enough to allow the scheduled level 0's to be dumped to holding disk. I'm in the enviable position of having over a week's worth of holding disk space. It was nice once when I forgot to change tape cartridges before a business trip. Had 6 amflush's to do to resyncronize. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: DLT8000s in a TL891 on Compaq kit running RedHat 7.3 Input/output error
On Thu, Aug 15, 2002 at 05:30:14PM +0100, Owen Williams wrote: The second is that I get problems using tapes from 'slot 9' of my 10 slot library. I have a cleaning tape in the tenth. I have two tape drives. I get: amcheck-server: slot 9: rewinding tape: Input/output error I got this first with amlabel. I configured amanda to use the other drive. I cleaned both drives and tried a new tape in 'slot 9' but I still get the 'rewinding input/output' error. I'm loathed to start backing things up while it still complains. Might your changer or changer script be calling the slots 0-9 rather than 1-10? In that case amanda might be trying to access the cleaning tape. BTW is the cleaning tape use frequently enough that you can't load it as needed? Then have a 10th tape in the changer. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Is this OK? Ignoring cruft file
On Thursday 15 August 2002 12:55, Frank Smith wrote: I've been corrected Frank, seems I'd missed the key word 'set', my bad. Can I plead alzheimers, or failing that, just plain stupidity? Maybe thats what I get for trying to keep my reading speeds up as the years pile up. :-) -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.11% setiathome rank, not too shabby for a WV hillbilly
Re: DLT8000s in a TL891 on Compaq kit running RedHat 7.3 Input/output error
On Thu, Aug 15, 2002 at 05:30:14PM +0100, Owen Williams wrote: The second is that I get problems using tapes from 'slot 9' of my 10 slot library. I have a cleaning tape in the tenth. I have two tape drives. I get: amcheck-server: slot 9: rewinding tape: Input/output error H, some changer/changer_script combos like to start at slot 0 and some like to start at slot 1. Are you sure you're not just off-by-one and you're trying to amcheck the cleaning tape? You could tell us your changer setup (both the changer.conf and the relevant bits of amanda.conf), and show us 'amtape config show'. And 'mtx status', if you're using mtx. Personally, I do *not* leave a cleaner in the library, and clean the tape drives once a year whether they need it or not. :-) Cleaning was essential and frequent in the old Exabyte 8x00 days (may they rot in hell forever), but I've literally never had a cleaning-related failure in DLT or LTO drives. (I've had bad *tapes*, though.) I got this first with amlabel. I configured amanda to use the other drive. I cleaned both drives and tried a new tape in 'slot 9' but I still get the 'rewinding input/output' error. I'm loathed to start backing things up while it still complains. If you're not off-by-one, and there really is some sort of anomaly where your changer script doesn't like slot 9, just tell it not to use slot 9 for now, and start doing backups. You can always update changer.conf later when you sort it out. -- Jay Lessert [EMAIL PROTECTED] Accelerant Networks Inc. (voice)1.503.439.3461 Beaverton OR, USA(fax)1.503.466.9472
Re: chg-zd-mtx output
Jason. In the amanda.conf file there is a entry for changer file. this must have entries that let the script (chg-zd-mtx) know how your tape changer works (ie needs an unload command or not, has a cleaner tape, etc). I'm including my 'CHANGER.conf' after this. EVERY option must have a 1 or a 0 you cannot leave any out. chris CHANGER.conf firstslot=1 lastslot=7 offlinestatus=1 havereader=0 autocleancount=200 AUTOCLEAN=0 OFFLINE_BEFORE_UNLOAD=1 cleanslot=8 Jason Greenberg wrote: Does anyone know what could cause this output? I am trying to debug my setup with a PowerVault 128T / Linux Redhat 7.3 bash-2.05a$ /usr/lib/amanda/chg-zd-mtx -info /usr/lib/amanda/chg-zd-mtx: [: : integer expression expected /usr/lib/amanda/chg-zd-mtx: [: -lt: unary operator expected 16 1 1 Jay
Re: DLT8000s in a TL891 on Compaq kit running RedHat 7.3 Input/outputerror
Hi, I got bitten by this when using arkeia, hoped I didn't this time. My confs are attached and here is the output from mtx status: # mtx status Storage Changer /dev/changer:2 Drives, 10 Slots ( 0 Import/Export ) Data Transfer Element 0:Empty Data Transfer Element 1:Empty Storage Element 1:Full :VolumeTag=A0 Storage Element 2:Full :VolumeTag=A1 Storage Element 3:Full :VolumeTag=A2 Storage Element 4:Full :VolumeTag=A3 Storage Element 5:Full :VolumeTag=A4 Storage Element 6:Full :VolumeTag=A5 Storage Element 7:Full :VolumeTag=A6 Storage Element 8:Full :VolumeTag=A7 Storage Element 9:Full :VolumeTag=A8 Storage Element 10:Full :VolumeTag=C0 Thanks for the very rapid response, Owen. # # amanda.conf - sample Amanda configuration file. This started off life as # the actual config file in use at CS.UMD.EDU. # # If your configuration is called, say, csd, then this file normally goes # in /etc/amanda/csd/amanda.conf. # org Blue # your organization name for reports mailto [EMAIL PROTECTED] # space separated list of operators at your site dumpuser amanda # the user to run dumps under inparallel 2# maximum dumpers that will run in parallel netusage 1000 Kbps # maximum net bandwidth for Amanda, in KB per sec dumpcycle 1 weeks # the number of days in the normal dump cycle runspercycle 1 weeks# the number of amdump runs in dumpcycle days tapecycle 9 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 ### ### ### # WARNING: don't use `inf' for tapecycle, it's broken! ### ### ### bumpsize 40 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. # Specify tape device and/or tape changer. If you don't have a tape # changer, and you don't want to use more than one tape per run of # amdump, just comment out the definition of tpchanger. # Some tape changers require tapedev to be defined; others will use # their own tape device selection mechanism. Some use a separate tape # changer device (changerdev), others will simply ignore this # parameter. Some rely on a configuration file (changerfile) to # obtain more information about tape devices, number of slots, etc; # others just need to store some data in files, whose names will start # with changerfile. For more information about individual tape # changers, read docs/TAPE.CHANGERS. # At most one changerfile entry must be defined; select the most # appropriate one for your configuration. If you select man-changer, # keep the first one; if you decide not to use a tape changer, you may # comment them all out. runtapes 1 # number of tapes to be used in a single run of amdump tpchanger chg-scsi# the tape-changer glue script tapedev 0 # the no-rewind tape device to be used #rawtapedev /dev/null # the raw device to be used (ftape only) #changerfile /var/lib/amanda/DailySet1/changer #changerfile /var/lib/amanda/DailySet1/changer-status changerfile /etc/amanda/Blue/chg-scsi.conf #changerdev /dev/sg0 tapetype DLT8000# what kind of tape it is (see tapetypes below) labelstr ^[AC][0-9][0-9][0-9][0-9][0-9]$ # label constraint regex: all tapes must match # Specify holding disks. These are used as a temporary staging area for # dumps before they are written to tape and are recommended for most sites. # The advantages include: tape drive is more likely to operate in streaming # mode (which reduces tape and drive wear, reduces total dump time); multiple # dumps can be done in parallel (which can dramatically reduce total dump time. # The main disadvantage is that dumps on the holding disk need to be flushed # (with amflush) to tape after an operating system crash or a tape failure. # If no holding disks are specified then all dumps will be written directly # to
Re: chg-zd-mtx output
On Thu, Aug 15, 2002 at 12:49:04PM -0400, Jason Greenberg wrote: Does anyone know what could cause this output? I am trying to debug my setup with a PowerVault 128T / Linux Redhat 7.3 bash-2.05a$ /usr/lib/amanda/chg-zd-mtx -info /usr/lib/amanda/chg-zd-mtx: [: : integer expression expected /usr/lib/amanda/chg-zd-mtx: [: -lt: unary operator expected 16 1 1 I'm a happy chg-zd-mtx user, but it is not the most portable script ever, because of: - The wide range of responses possible from a dizzying array of almost-but-not-quite standards compliant changers. - The wide range of responses possible from a disturbingly variant range of tr, sed, awk, sh, etc. utilities. When I was tweaking my chg-zd-mtx to work, what I found most useful was: % cd /usr/local/etc/amanda/config_dir % sh -x /usr/lib/amanda/chg-zd-mtx -info (or whatever command doesn't work) In your case, the problem is probably *not* in the line like: if [ $usedslot -lt 0 ]; then where the script is blowing up, but in the mildly amazing line like: usedslot=`echo $tmpslot | sed -n s/Data Transfer Element $drivenum:Empty/-1/p; s/Data Transfer Element $drivenum:Full (Storage Element \([1-9][0-9]*\) Loaded)\(.*\)/\1/p` where the sed is not interacting w/the mtx output from your changer the way the script expects. -- Jay Lessert [EMAIL PROTECTED] Accelerant Networks Inc. (voice)1.503.439.3461 Beaverton OR, USA(fax)1.503.466.9472
Request for explanation of Index tee error
What does the following syslog errors mean? Should I be concerned about it/do something to fix it? Aug 13 00:56:10 ivideo sendbackup[3608]: index tee cannot write [Connection reset by peer] Aug 14 01:00:43 vision sendbackup[1630]: index tee cannot write [Connection reset by peer] Aug 15 00:55:16 vision sendbackup[3042]: index tee cannot write [Connection reset by peer] Michael Martinez System Administrator (Contractor) Information Systems and Technology Management CSREES - United States Department of Agriculture (202) 720-6223
Re: DLT8000s in a TL891 on Compaq kit running RedHat 7.3 Input/output error
On Thursday 15 August 2002 13:00, Gene Heskett wrote: Hummm, there is a 'startuse' in mine, currently set for 0. Does anyone know if this is the starting slot, or is it the number offset to be added to all further slot numbering schemes? If its the base 0/base 1 switch, a lot of changer vs newbie problems would be solved. Inquiring minds, even this old one, want to know... I had this idea that if I changed the startuse and enduse and cleaningtape numbers in chg-scsi.conf, that the startuse would adjust the numbering base. Alas it didn't, so now the regularly scheduled program will resume. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.11% setiathome rank, not too shabby for a WV hillbilly
Re: Request for explanation of Index tee error
On Thu, Aug 15, 2002 at 01:54:56PM -0400, Martinez, Michael - CSREES/ISTM wrote: What does the following syslog errors mean? Should I be concerned about it/do something to fix it? Aug 13 00:56:10 ivideo sendbackup[3608]: index tee cannot write [Connection reset by peer] Aug 14 01:00:43 vision sendbackup[1630]: index tee cannot write [Connection reset by peer] Aug 15 00:55:16 vision sendbackup[3042]: index tee cannot write [Connection reset by peer] Don't know why it is happening, but here is what I think is happening. The data from your dumper program, dump/ufsdump/tar/???, passes through a program that duplicates the entire data set and sends each through a separate data stream (pipes/sockets/...). Similar to the unix tee program. One stream goes to the holding disk/tape drive. The duplicate stream goes to the undumper program to generate a table of contents. This TOC is massaged and becomes the index for the dump. For some reason this second stream is unable to write its output (or temporary files). This could be a permission problem, a wrong path with missing directories, a full file system or ??? HTH -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: DLT8000s in a TL891 on Compaq kit running RedHat 7.3 Input/output error
On Thu, Aug 15, 2002 at 06:15:05PM +0100, Owen Williams wrote: # mtx status Storage Changer /dev/changer:2 Drives, 10 Slots ( 0 Import/Export ) Data Transfer Element 0:Empty Data Transfer Element 1:Empty Storage Element 1:Full :VolumeTag=A0 Storage Element 2:Full :VolumeTag=A1 Storage Element 3:Full :VolumeTag=A2 Storage Element 4:Full :VolumeTag=A3 Storage Element 5:Full :VolumeTag=A4 Storage Element 6:Full :VolumeTag=A5 Storage Element 7:Full :VolumeTag=A6 Storage Element 8:Full :VolumeTag=A7 Storage Element 9:Full :VolumeTag=A8 Storage Element 10:Full :VolumeTag=C0 [clip] runtapes 1# number of tapes to be used in a single run of amdump tpchanger chg-scsi # the tape-changer glue script OK, I *think* you're off-by-one. tapedev 0 # the no-rewind tape device to be used #changerdev /dev/sg0 [clip] config0 drivenum 0 startuse 0 # The slots associated with the drive 0 enduse9 # cleancart 9 # the slot where the cleaningcartridge for drive 0 is located So the changer thinks first slot is 1, but you've said 'startuse 0'. when you go 'amtape DailySet1 slot first' and 'slot last', and you go physically watch the robot, which tapes move? Besides which, if you *are* going to use cleancart (and I'm not sure it really works in Amanda at all), I'm pretty sure enduse == cleancart is not right. -- Jay Lessert [EMAIL PROTECTED] Accelerant Networks Inc. (voice)1.503.439.3461 Beaverton OR, USA(fax)1.503.466.9472
Problem dumping one filesystem on a host
I'm having trouble backing up one particular filesystem on a host (FreeBSD 4.6-STABLE). In particular, every time I run amdump, I get this result: FAILURE AND STRANGE DUMP SUMMARY: kanga.int da0s1e lev 0 FAILED [disk da0s1e offline on kanga.int?] Now, I've read the Amanda Faq-O-Matic entry for this error, but I still can't see what's going on. Here is the portion of my disklist file with the relevant filesystems. Note that the entry for da0s1e is identical to that of ad0s1a except for the device name. # / kanga.int ad0s1a compressed-tar -1 local # /tmp kanga.int vinum/tmp compressed-tar -1 local # /home kanga.int vinum/home compressed-tar -1 local # /usr kanga.int vinum/usr compressed-tar -1 local # /usr/export kanga.int vinum/usr_export compressed-tar -1 local # /usr/obj kanga.int vinum/usr_obj compressed-tar -1 local # /usr/src kanga.int vinum/usr_src compressed-tar -1 local # /var kanga.int vinum/var compressed-tar -1 local # /usr/export/vserver2/home/freenet/store kanga.int da0s1e compressed-tar -1 local # Special large directories kanga.int /usr/share compressed-tar-with-excludes -1 local kanga.int /usr/share/media uncompressed-tar-with-excludes -1 local kanga.int /usr/share/media/music/all uncompressed-tar -1 local Here are the log entries I'm getting, but they don't seem to say much: INFO planner Adding new disk kanga.int:da0s1e. INFO planner Incremental of pooh.int:volgroup1/usr_stripe32k bumped to level 2. INFO planner Incremental of pooh.int:volgroup1/var_stripe32k bumped to level 2. INFO planner Incremental of pooh.int:volgroup1/tmp_stripe32k bumped to level 2. INFO planner Incremental of kanga.int:vinum/home bumped to level 2. FAIL planner kanga.int da0s1e 20020815 0 [disk da0s1e offline on kanga.int?] I've checked for permission problems, but ownership and perms are identical on ad0s1a (which works correctly) and da0s1e (which fails): root@kanga:/var/amanda# ls -la /dev/ad0s1a /dev/da0s1e crw-r- 2 root operator 116, 0x0002 Aug 9 10:41 /dev/ad0s1a crw-r- 2 root operator 13, 0x00020004 Aug 9 10:41 /dev/da0s1e I've also fscked that partition without a change in the results: root@kanga:/var/amanda# umount /dev/da0s1e; fsck /dev/da0s1e; mount /dev/da0s1e ** /dev/da0s1e ** Last Mounted on /usr/export/vserver2/home/freenet/store ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 9 files, 2098241 used, 2004845 free (13 frags, 250604 blocks, 0.0% fragmentation) Finally, the drive itself is rather small (4GB), and the individual files contained therein are not particularly large: root@kanga:/var/amanda# ls -al /usr/export/vserver2/home/freenet/store total 2098242 drwxr-s--- 2 1100 media512 Aug 11 23:46 . drwx-- 7 1100 media 1024 Aug 12 09:41 .. -rw-r--r-- 1 1100 media 268435456 Aug 13 09:18 part0 -rw-r--r-- 1 1100 media 268435456 Aug 13 09:18 part1 -rw-r--r-- 1 1100 media 268435456 Aug 13 09:18 part2 -rw-r--r-- 1 1100 media 268435456 Aug 11 23:11 part3 -rw-r--r-- 1 1100 media 268435456 Aug 11 23:23 part4 -rw-r--r-- 1 1100 media 268435456 Aug 11 23:35 part5 -rw-r--r-- 1 1100 media 268435456 Aug 11 23:46 part6 -rw-r--r-- 1 1100 media 268435456 Aug 11 23:58 part7 I'm flummoxed. I just can't see why I can't backup this filesystem, which is indentical in many ways to other filesystems that get saved nightly. Any ideas what else I might look for? -- Kirk Strauser The Strauser Group - http://www.strausergroup.com/
Labels and Barcodes
What's the difference between labels and barcodes? Why, when I label tapes, does the VolumeTag= not show up for that tape?
Re: Holding Disk Question
My motto: Disk is cheap, don't skimp on holding disk. Yup... after I deployed a 181 GB drive for our holding disk, I saw somewhat different behavior in amstatus... though I would have expected the total time of the backups to drop (compared to a relatively small 25 GB holding space I used before) they did not... I conclude this was because the entire run is tape i/o bound... Holding disk usage on the runs with this disk were about 90% capacity... so the clients were not taking so long to complete their data transfers... This would seem to indicate I need to double this amount of space to hold 2 days of backups, currently... I'd like to have a week's worth, actually in case the tape goes South and replacement is not easy and quick. So does the chunksize parameter affect performance in any way? thx --
Re: chg-zd-mtx output
On Thu, Aug 15, 2002 at 12:49:04PM -0400, Jason Greenberg wrote: Does anyone know what could cause this output? I am trying to debug my setup with a PowerVault 128T / Linux Redhat 7.3 bash-2.05a$ /usr/lib/amanda/chg-zd-mtx -info /usr/lib/amanda/chg-zd-mtx: [: : integer expression expected /usr/lib/amanda/chg-zd-mtx: [: -lt: unary operator expected 16 1 1 I'll take a chance of clarifying instead of muddying this issue From what I have been learning from some FINE people on this list about shell scripting is... that the error above is likely caused by a string of length zero as one of the variables in the test. If the source was written with by prepending 'x' on both variables such that the value of the variables would be concatenated with the 'x', the broken test would not likely occur. I think this explanation is accurate but it needs review. where the script is blowing up, but in the mildly amazing line like: usedslot=`echo $tmpslot | sed -n s/Data Transfer Element $drivenum:Empty/-1/p; s/Data Transfer Element $drivenum:Full (Storage Element \([1-9][0-9]*\) Loaded)\(.*\)/\1/p` Now, broken-ness at this point may indicate the media changer's output is not compatible with the chosen amtape changer glue code module... where the sed is not interacting w/the mtx output from your changer the way the script expects. yes --
Re: Labels and Barcodes
--On Thursday, August 15, 2002 14:52:26 -0400 Jason Greenberg [EMAIL PROTECTED] wrote: What's the difference between labels and barcodes? Why, when I label tapes, does the VolumeTag= not show up for that tape? As I understand it, the 'label' is the header record that is the first record on the tape. 'barcode' is the paper barcode on the outside of the tape. Some changer scripts can associate the two if you have a barcode reader in your library, some can't. Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
amrecover for rescue disk
Someone did a rescue disk for amanda? I need to restore a host on a new HD. tanks -- Dominique Arpin___[espace gestionnaire réseau courbe] http://www.espacecourbe.com/ téléphone514.933.9861 télécopieur 514.933.9546
Re: chg-zd-mtx output
On Thu, Aug 15, 2002 at 11:36:23AM -0700, John Koenig wrote: On Thu, Aug 15, 2002 at 12:49:04PM -0400, Jason Greenberg wrote: Does anyone know what could cause this output? I am trying to debug my setup with a PowerVault 128T / Linux Redhat 7.3 bash-2.05a$ /usr/lib/amanda/chg-zd-mtx -info /usr/lib/amanda/chg-zd-mtx: [: : integer expression expected /usr/lib/amanda/chg-zd-mtx: [: -lt: unary operator expected 16 1 1 I'll take a chance of clarifying instead of muddying this issue From what I have been learning from some FINE people on this list about shell scripting is... that the error above is likely caused by a string of length zero as one of the variables in the test. This is likely true, though the first one integer expression expected could be caused by a word where a number is expected or the empty string. If the source was written with by prepending 'x' on both variables such that the value of the variables would be concatenated with the 'x', the broken test would not likely occur. I think this explanation is accurate but it needs review. As both cases above are expecting integers putting an x into a currently empty integer field would change the error, not correct it. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Holding Disk Question
On Thu, Aug 15, 2002 at 11:49:15AM -0700, John Koenig wrote: So does the chunksize parameter affect performance in any way? Not to my knowledge. It is a patch for holding disks with limited file size maximums, often 2GB. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Request for explanation of Index tee error
I can't give a good explanation at this point but symptoms include but are not limited to: blood-shot eyes, blurry vision, headaches. :-) Keep us posted as to yuor findings. Good Luck, Jim On Thu, 2002-08-15 at 12:54, Martinez, Michael - CSREES/ISTM wrote: What does the following syslog errors mean? Should I be concerned about it/do something to fix it? Aug 13 00:56:10 ivideo sendbackup[3608]: index tee cannot write [Connection reset by peer] Aug 14 01:00:43 vision sendbackup[1630]: index tee cannot write [Connection reset by peer] Aug 15 00:55:16 vision sendbackup[3042]: index tee cannot write [Connection reset by peer] Michael Martinez System Administrator (Contractor) Information Systems and Technology Management CSREES - United States Department of Agriculture (202) 720-6223
Re: Holding Disk Question
On Thu, 15 Aug 2002, John Koenig wrote: Yup... after I deployed a 181 GB drive for our holding disk, I saw somewhat different behavior in amstatus... though I would have expected the total time of the backups to drop (compared to a relatively small 25 GB holding space I used before) they did not... I conclude this was because the entire run is tape i/o bound... Holding disk usage on the runs with this disk were about 90% capacity... so the clients were not taking so long to complete their data transfers... This would seem to indicate I need to double this amount of space to hold 2 days of backups, currently... I'd like to have a week's worth, actually in case the tape goes South and replacement is not easy and quick. So does the chunksize parameter affect performance in any way? No. Taping of a dump spooled to holding disk does not begin until all chunks are received. The best way to figure out where your bottleneck and what configuration changes will give you the greatest return is is to run amplot. It will give you a graphical representation of what's happening when. Very revealing. -Mitch
Re: Run and dump cycle recommendations?
Hi Jon, thanks for the reply. On Tue, 2002-08-13 at 16:20, Jon LaBadie wrote: You have 11 machines, the tape server and 10 clients. Say on average each has 4 file systems. You would then have 44 items (host/filesystem) to backup. These would each be listed in a file called disklist. So where, if at all, does this disklist file get referenced in the amanda.conf? And where should it live? Backups, called dumps regardless of the backup program (dump or tar) are performed at levels. A full dump (everything on a disklist entry) is a level 0 (zero). Others levels are known as incrementals, level 1 means everything changed since the last level 0. Level 2 dumps are everything changed since the last level 1. Gotcha -- that all makes sense. But in what instance would one want to do a level 2 as opposed to just a level 1? All this info is collected in a file called amanda.conf. Here's where I'm stuck now. As I'm just beginning, my test amanda.conf configuration is as follows: tpchanger chg-manual # This will hopefully change after testing tapedev /dev/sg0 tapetype DAT changerfile /etc/amanda/DailySet1/changer.conf And here's my changer.conf: number_configs 1 eject 0 # Tapedrives need an eject command sleep 90 # Seconds to wait until the tape gets ready cleanmax100 # How many times could a cleaning tape get used changerdev /dev/sg0 # # Next comes the data for drive 0 # config 0 drivenum0 dev /dev/nst0 # dev /dev/ns0 scsitapedev /dev/sg0 startuse0 # The slots associated with the drive 0 enduse 7 # statfile/etc/amanda/DailySet1/tape0-slot # The file where the actual slot is stored cleancart 8 # the slot where the cleaningcartridge for drive 0 is located cleanfile /etc/amanda/DailySet1/tape0-clean # The file where the cleanings are recorded usagecount /etc/amanda/DailySet1/totaltime tapestatus /etc/amanda/DailySet1/tapestatus # here will some status infos be stored #labelfile /etc/amanda/DailySet1/labelfile # Use this if you have an barcode reader But when I run 'amcheck -s DailySet1', I get this error: Holding disk /backup/amanda: 12891648 KB disk space available, using 7771648 KB amcheck-server: could not get changer info: badly formed result from changer: /usr/lib/amanda/chg-manual: number_configs: command not found I have no idea what that means, but there really is no command called number_configs on this box. I've tried changing tpchanger to chg-scsi and chg-multi (as I really don't know which one I'll want to be using in the future), but haven't had any success with those either. With this as a starting point, get the source code, and in a directory called docs are many information documents. An important one is INSTALLATION. Also see the example amanda.conf file for all its comment remarks. Thanks again, Jon -- you've helped a great deal already. Cheers, -Charlie
Re: Run and dump cycle recommendations?
On Thu, Aug 15, 2002 at 01:38:40PM -0700, Charlie Bebber wrote: Hi Jon, thanks for the reply. On Tue, 2002-08-13 at 16:20, Jon LaBadie wrote: You have 11 machines, the tape server and 10 clients. Say on average each has 4 file systems. You would then have 44 items (host/filesystem) to backup. These would each be listed in a file called disklist. So where, if at all, does this disklist file get referenced in the amanda.conf? And where should it live? named disklist, same dir as amanda.conf aka configdir. Backups, called dumps regardless of the backup program (dump or tar) are performed at levels. A full dump (everything on a disklist entry) is a level 0 (zero). Others levels are known as incrementals, level 1 means everything changed since the last level 0. Level 2 dumps are everything changed since the last level 1. Gotcha -- that all makes sense. But in what instance would one want to do a level 2 as opposed to just a level 1? You don't, amanda does. Bases it on size of respective levels. Yesterday's level 1 might have been 50MB. Today's 55MB. But maybe a level 2 today would only be 10MB. All this info is collected in a file called amanda.conf. Here's where I'm stuck now. As I'm just beginning, my test amanda.conf configuration is as follows: Start off with no changer, just a tapedev. Simpler for cutting your teeth. tpchanger chg-manual# This will hopefully change after testing tapedev /dev/sg0 tapetype DAT changerfile /etc/amanda/DailySet1/changer.conf And here's my changer.conf: number_configs 1 eject 0 # Tapedrives need an eject command sleep 90 # Seconds to wait until the tape gets ready cleanmax100 # How many times could a cleaning tape get used changerdev /dev/sg0 # # Next comes the data for drive 0 # config 0 drivenum0 dev /dev/nst0 # dev /dev/ns0 scsitapedev /dev/sg0 startuse0 # The slots associated with the drive 0 enduse 7 # statfile/etc/amanda/DailySet1/tape0-slot # The file where the actual slot is stored cleancart 8 # the slot where the cleaningcartridge for drive 0 is located cleanfile /etc/amanda/DailySet1/tape0-clean # The file where the cleanings are recorded usagecount /etc/amanda/DailySet1/totaltime tapestatus /etc/amanda/DailySet1/tapestatus # here will some status infos be stored #labelfile /etc/amanda/DailySet1/labelfile # Use this if you have an barcode reader But when I run 'amcheck -s DailySet1', I get this error: Holding disk /backup/amanda: 12891648 KB disk space available, using 7771648 KB amcheck-server: could not get changer info: badly formed result from changer: /usr/lib/amanda/chg-manual: number_configs: command not found I have no idea what that means, but there really is no command called number_configs on this box. But chg-manual is trying to execute one. I have never used chg-manual before. I was able to reproduce your situation. I believe it has a MAJOR defect, so major that I wonder if anyone has used chg-manual successfully. I'm going to ask the list. As I suggested above, work with no changer for now or jump right in to your final changer config. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
chg-manual has anyone used it successfully?
Investigating a recent posting I looked at the chg-manual code. It contains the following: if [ -f $changerfile ]; then . $changerfile fi $changerfile is configdir/changer.conf normally. It is being sourced in this code such that the lines should be shell script syntax. But changer.conf is not a shell script. Instead it contains lines like: number_configs 1 which the sourcing tries to execute like a command line and of course there is no program called number_configs. It appears that the author of chg-manual expected the syntax of changer.conf to be parameter assignments like NUM_CONFIG=1. Has anyone been using chg-manual? HOW? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Sun L20 and amanda
Hello, I have configured amanda 2.4.3b3 to use the DLT8000 in the library. The next step is to get the changer working. I wasn't able to get mtx working with the L20. If anyone if currently using the L20 library with amanda, or if you have suggestions on how to configure the tape library changer, I'd really appreciate it. Anne Hammond University of Colorado at Boulder
Re: Labels and Barcodes
On 15 Aug 2002, Jason Greenberg wrote: - What's the difference between labels and barcodes? Why, when I label - tapes, does the VolumeTag= not show up for that tape? To amanda, a label is the information in the fist part of a tape. It identifies what backup set the tape belongs to, when it was last used, etc. Labels have nothing to do with the 'Volume Tag which are from the barcodes. -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
Re: Sun L20 and amanda
On Thu, Aug 15, 2002 at 04:12:01PM -0600, Anne M. Hammond wrote: Hello, I have configured amanda 2.4.3b3 to use the DLT8000 in the library. The next step is to get the changer working. I wasn't able to get mtx working with the L20. If anyone if currently using the L20 library with amanda, or if you have suggestions on how to configure the tape library changer, I'd really appreciate it. I'm currently running Sparc Solaris 8, L20 w/LTO, 2.4.2p2, mtx-1.2.16rel, chg-zd-mtx. Drop me a line off-list w/any specific questions, you can summarize to the list later. -Jay- -- Jay Lessert [EMAIL PROTECTED] Accelerant Networks Inc. (voice)1.503.439.3461 Beaverton OR, USA(fax)1.503.466.9472
Re: Run and dump cycle recommendations?
On Thu, 2002-08-15 at 14:16, Jon LaBadie wrote: Start off with no changer, just a tapedev. Simpler for cutting your teeth. Ok, so I commented that out and have gotten a little further (or so it seems). Perhaps I'm getting ahead of myself. With the tapdev set to /dev/sg0 , when I run 'amcheck -s DailySet1', I get the following: --- Holding disk /backup/amanda: 12891648 KB disk space available, using 7771648 KB ERROR: /dev/sg0: rewinding tape: Permission denied (expecting a new tape) NOTE: skipping tape-writable test NOTE: info dir /var/lib/amanda/DailySet1/curinfo: does not exist NOTE: it will be created on the next run NOTE: index dir /var/lib/amanda/DailySet1/index/localhost: does not exist Server check took 30.107 seconds --- After seeing that /dev/sg0 is a rewinding device and reading in INSTALL that it needs to point to a non-rewinding device, I changed it to point to /dev/nst0 which is supposedly it in linux. However, when 'amcheck -s DailySet' is run again, I get this: --- Holding disk /backup/amanda: 12891648 KB disk space available, using 7771648 KB ERROR: /dev/nst0: rewinding tape: No medium found (expecting a new tape) NOTE: skipping tape-writable test NOTE: info dir /var/lib/amanda/DailySet1/curinfo: does not exist NOTE: it will be created on the next run NOTE: index dir /var/lib/amanda/DailySet1/index/localhost: does not exist Server check took 30.246 seconds --- At least with /dev/sg0, it had found a medium. And I'm not too sure what's going on with the permission denied error either. Here's the 'id' of the amanda user: uid=33(amanda) gid=6(disk) groups=6(disk) And the perms for /dev/sg0 are: crw-rw1 root disk 21, 0 Aug 30 2001 /dev/sg0 So that should be fine, shouldn't it? Doesn't it just need for the group's read and write bits to be set? I've even set it to 4777 and still get the permission denied error. Any ideas on this one? Do you need to label the tapes before running 'amcheck'? As I suggested above, work with no changer for now or jump right in to your final changer config. I figured I'd play with the final changer config once I'd gotten amanda to work at all, but just out of curiosity, does anyone have any idea as to what I might use with this external ultra160 SCSI Compaq eight cassette autoloader in linux? I'm presuming chg-scsi, but I haven't had much luck with my presumptions recently. Thanks again, everyone (especially Jon). -Charlie
Re: Run and dump cycle recommendations?
After seeing that /dev/sg0 is a rewinding device and reading in INSTALL that it needs to point to a non-rewinding device, I changed it to point to /dev/nst0 which is supposedly it in linux. However, when 'amcheck -s DailySet' is run again, I get this: --- Holding disk /backup/amanda: 12891648 KB disk space available, using 7771648 KB ERROR: /dev/nst0: rewinding tape: No medium found (expecting a new tape) NOTE: skipping tape-writable test NOTE: info dir /var/lib/amanda/DailySet1/curinfo: does not exist NOTE: it will be created on the next run NOTE: index dir /var/lib/amanda/DailySet1/index/localhost: does not exist Server check took 30.246 seconds --- At least with /dev/sg0, it had found a medium. And I'm not too sure what's going on with the permission denied error either. Was there a tape inserted into the drive at this point? Had it been amlabel'ed hopefully that is what is missing at this juncture... ? --
Re: DLT8000s in a TL891 on Compaq kit running RedHat 7.3 Input/output error
On Thursday 15 August 2002 14:22, Jay Lessert wrote: On Thu, Aug 15, 2002 at 06:15:05PM +0100, Owen Williams wrote: # mtx status Storage Changer /dev/changer:2 Drives, 10 Slots ( 0 Import/Export ) Data Transfer Element 0:Empty Data Transfer Element 1:Empty Storage Element 1:Full :VolumeTag=A0 Storage Element 2:Full :VolumeTag=A1 Storage Element 3:Full :VolumeTag=A2 Storage Element 4:Full :VolumeTag=A3 Storage Element 5:Full :VolumeTag=A4 Storage Element 6:Full :VolumeTag=A5 Storage Element 7:Full :VolumeTag=A6 Storage Element 8:Full :VolumeTag=A7 Storage Element 9:Full :VolumeTag=A8 Storage Element 10:Full :VolumeTag=C0 [clip] runtapes 1 # number of tapes to be used in a single run of amdump tpchanger chg-scsi # the tape-changer glue script OK, I *think* you're off-by-one. tapedev 0 # the no-rewind tape device to be used #changerdev /dev/sg0 [clip] config 0 drivenum 0 startuse 0 # The slots associated with the drive 0 enduse 9 # cleancart9 # the slot where the cleaningcartridge for drive 0 is located So the changer thinks first slot is 1, but you've said 'startuse 0'. when you go 'amtape DailySet1 slot first' and 'slot last', and you go physically watch the robot, which tapes move? FYI, it appears that the chg-scsi utility runs in a base 0 numbering mode. Here as I just tested it using amtape /config/ scan, setting the startuse to 1 (which matches the displayed on the front of the robot number for the first cart in the magazine) resulted in its not even looking at what chg-scsi calls Slot 0 which was already loaded, but it advanced the mechanism and loaded the second tape, then proceeded to report it as tape so-and-so in Slot 0. Besides which, if you *are* going to use cleancart (and I'm not sure it really works in Amanda at all), I'm pretty sure enduse == cleancart is not right. No, enduse must be one less than cleancart, so his last valid tape is in slot 8 in a 0-9 numbered string of 10 slots. Autoclean ATM it is not working automaticly, it seems that every drive vendor has their own idea of howto define and report the sort of error rates that would be used to indicate a need for cleaning, hence no quick and dirty read of the drives main status page seems to be possible. mt for instance see's no reportable difference in my drives status before, or after I've extinguished the blinking led on the face of the drawer with a cleaning cycle. There are sub-pages I'm told, but it appears there is no standard way of formatting the reported data. I was hoping that Thomas Hepper might find time to do something with that as I'd sent him the full doc package on my Seagate CTL-96 some time back, but then his job got to be about 7/12's or worse and he really hasn't had the time to address it. But be aware that there seem to be wide vendor diffs about this items reporting, and even if it can be made to work with my drive, it will probably fall on its collective face when querying a DLT or whathaveyou drive. In the meantime, having a cleaning tape in the last slot is handy, but its still a manual operation to use it. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.11% setiathome rank, not too shabby for a WV hillbilly
Re: Holding Disk Question
On Thursday 15 August 2002 14:49, John Koenig wrote: My motto: Disk is cheap, don't skimp on holding disk. Yup... after I deployed a 181 GB drive for our holding disk, I saw somewhat different behavior in amstatus... though I would have expected the total time of the backups to drop (compared to a relatively small 25 GB holding space I used before) they did not... I conclude this was because the entire run is tape i/o bound... Holding disk usage on the runs with this disk were about 90% capacity... so the clients were not taking so long to complete their data transfers... This would seem to indicate I need to double this amount of space to hold 2 days of backups, currently... I'd like to have a week's worth, actually in case the tape goes South and replacement is not easy and quick. So does the chunksize parameter affect performance in any way? Only in that it prevents troubles with a filesystem that can't handle large files. There was, at the time amanda was first deployed, a 2gig limit to the filesize in many of its various platforms filesystems. Many of those limits are now historical, but you'd hate to find it out by doing a recovery and having it blow up because a tape of 20gigs was all one big file. thx -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.11% setiathome rank, not too shabby for a WV hillbilly
Re: Holding Disk Question
On Thu, 15 Aug 2002, Gene Heskett wrote: On Thursday 15 August 2002 14:49, John Koenig wrote: So does the chunksize parameter affect performance in any way? Only in that it prevents troubles with a filesystem that can't handle large files. There was, at the time amanda was first deployed, a 2gig limit to the filesize in many of its various platforms filesystems. Many of those limits are now historical, but you'd hate to find it out by doing a recovery and having it blow up because a tape of 20gigs was all one big file. A 20 GB dump _is_ all one big file. Chunking is only implemented on the holding disk during dumping. The chunks are merged back into a single file when spooled from holding disk to tape. When you do a recovery what comes back is a single large file. If you want to recover the whole dump from tape to your holding disk before pulling out the files that need to be restored, then you'll have to split it up by hand in the process. -Mitch
