Re: TCP Port Usage
Hi, AFAIK the portrange settings have to be applied identically at the server and the client. You have recompiled the client with the same settings for portrange, correct? Christoph Dean Pullen schrieb: Hi all. I have compiled Amanda using the following options: ./configure --with-user=amanda \ --mandir=/usr/share/man \ --prefix=/usr \ --infodir=/usr/share/info \ --sysconfdir=/etc \ --libdir=/usr/lib \ --libexecdir=/usr/lib/amanda \ --localstatedir=/var/lib \ --with-index-server=admin01 \ --with-gnutar-listdir=/var/lib/amanda/gnutar-lists \ --with-smbclient=/usr/bin/smbclient \ --with-amandahosts \ --with-gnutar=/bin/tar \ --with-group=disk \ --with-owner=amanda \ --with-tape-device=/dev/nst0 \ --with-debugging=/tmp/amanda \ --with-tape-server=admin01 \ --with-configdir=/etc/amanda \ --with-tcpportrange=52000,6 \ --with-udpportrange=850,851 As you can see, I've ensured the tcp port-range used is between 52000 and 6. There are no problems when using amcheck. However, when trying to use amdump, I cannot connect to the client and my firewall reports the following packet drops: Shorewall:all2all:REJECT:IN= OUT=bond1 SRC=192.168.100.1 DST=192.168.100.20 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=14897 DF PROTO=TCP SPT=55003 DPT=46882 WINDOW=5840 RES=0x00 SYN URGP=0 i.e. packet from Amanda server source port 55003 (within the range I built Amanda with) is trying to be sent to the client on client port 46882 - why is Amanda trying to use this port when I have configured it not to? Thanks for any replies in advance. Dean Pullen
amrecover
What have I done wrong in this case? [EMAIL PROTECTED] amanda]# su - [EMAIL PROTECTED] root]# amrecover tagesbackup AMRECOVER Version 2.4.3. Contacting server on localhost ... 220 amd450 AMANDA index server (2.4.3) ready. 500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed [EMAIL PROTECTED] root]# whoami root [EMAIL PROTECTED] root]# entries in my .amandahosts file: localhost amanda localhost root localhost.localdomain amanda localhost.localdomain root backupstorm.medienpartner.de amanda backupstorm.medienpartner.de root backupstorm root backupstorm amanda amd450.medienpartner.de amanda amd450.medienpartner.de root With regards and thanks in advance to the one who hast the right answer pascal
RE: TCP Port Usage
Hm I certainly presumed I had (did it a while back). I will go back and ensure I have. -Original Message- From: Christoph Scheeder [mailto:[EMAIL PROTECTED] Sent: 07 April 2004 07:00 To: Dean Pullen Cc: [EMAIL PROTECTED] Subject: Re: TCP Port Usage Hi, AFAIK the portrange settings have to be applied identically at the server and the client. You have recompiled the client with the same settings for portrange, correct? Christoph Dean Pullen schrieb: Hi all. I have compiled Amanda using the following options: ./configure --with-user=amanda \ --mandir=/usr/share/man \ --prefix=/usr \ --infodir=/usr/share/info \ --sysconfdir=/etc \ --libdir=/usr/lib \ --libexecdir=/usr/lib/amanda \ --localstatedir=/var/lib \ --with-index-server=admin01 \ --with-gnutar-listdir=/var/lib/amanda/gnutar-lists \ --with-smbclient=/usr/bin/smbclient \ --with-amandahosts \ --with-gnutar=/bin/tar \ --with-group=disk \ --with-owner=amanda \ --with-tape-device=/dev/nst0 \ --with-debugging=/tmp/amanda \ --with-tape-server=admin01 \ --with-configdir=/etc/amanda \ --with-tcpportrange=52000,6 \ --with-udpportrange=850,851 As you can see, I've ensured the tcp port-range used is between 52000 and 6. There are no problems when using amcheck. However, when trying to use amdump, I cannot connect to the client and my firewall reports the following packet drops: Shorewall:all2all:REJECT:IN= OUT=bond1 SRC=192.168.100.1 DST=192.168.100.20 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=14897 DF PROTO=TCP SPT=55003 DPT=46882 WINDOW=5840 RES=0x00 SYN URGP=0 i.e. packet from Amanda server source port 55003 (within the range I built Amanda with) is trying to be sent to the client on client port 46882 - why is Amanda trying to use this port when I have configured it not to? Thanks for any replies in advance. Dean Pullen
Re: amrecover
Hi, you are missing the line amd450 root in your .amandahosts file. Christoph pascal thomas schrieb: What have I done wrong in this case? [EMAIL PROTECTED] amanda]# su - [EMAIL PROTECTED] root]# amrecover tagesbackup AMRECOVER Version 2.4.3. Contacting server on localhost ... 220 amd450 AMANDA index server (2.4.3) ready. 500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed [EMAIL PROTECTED] root]# whoami root [EMAIL PROTECTED] root]# entries in my .amandahosts file: localhost amanda localhost root localhost.localdomain amanda localhost.localdomain root backupstorm.medienpartner.de amanda backupstorm.medienpartner.de root backupstorm root backupstorm amanda amd450.medienpartner.de amanda amd450.medienpartner.de root With regards and thanks in advance to the one who hast the right answer pascal
Re: amrecover
On Wednesday 07 April 2004 03:40, pascal thomas wrote: What have I done wrong in this case? [EMAIL PROTECTED] amanda]# su - [EMAIL PROTECTED] root]# amrecover tagesbackup AMRECOVER Version 2.4.3. Contacting server on localhost ... 220 amd450 AMANDA index server (2.4.3) ready. 500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed [EMAIL PROTECTED] root]# whoami root [EMAIL PROTECTED] root]# entries in my .amandahosts file: localhost amanda localhost root localhost.localdomain amanda localhost.localdomain root And once again, the docs and the FAQ are ignored. The use of localhost will bite you, and just did. Replace that with the FQDN, resolvable in the /etc/hosts file, or with the machines ip address. There may be other problems, but thats the first step. backupstorm.medienpartner.de amanda backupstorm.medienpartner.de root backupstorm root backupstorm amanda amd450.medienpartner.de amanda amd450.medienpartner.de root With regards and thanks in advance to the one who hast the right answer pascal -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) 99.22% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
Clean drive
I came to my weekly autoloader change and noticed 'Clean Required' on the panel. The changer is a 8 slot DDS4 changer and slot 8 houses the cleaning tape. I ran $ amtape clean and got amtape: device 8 not clean: Cleaning Cartridge Installed and Ejected I'm not actually there now, did this remotely so can't see if it still says 'Clean Required' Does anyone know what that message means? thanks Tom
AIT-2
Hi, I'm currently having problems restoring files from my amanda backup system. I am able to narrow the problem down to my AIT-2 tape drive. If I restore files from amanda backups that are still on the holding disk, I have a successful restore. If I restore files from any of the AIT-2 tapes, I get tar errors. So I have a few questions: 1) When amanda uses tar to backup the data, what is the blocking size that amanda uses? 2) If anyone here is using an sdx-500 AIT-2 tape drive, what are your dip switches set to? (I'm wondering if I need to enable variable block sizing on the drive). 3) Has anyone else using an AIT tape drive had similar problems? Thanks -Rob
Re: AIT-2
--On Wednesday, April 07, 2004 11:25:10 -0700 Dege, Robert C. [EMAIL PROTECTED] wrote: Hi, I'm currently having problems restoring files from my amanda backup system. I am able to narrow the problem down to my AIT-2 tape drive. If I restore files from amanda backups that are still on the holding disk, I have a successful restore. If I restore files from any of the AIT-2 tapes, I get tar errors. So I have a few questions: 1) When amanda uses tar to backup the data, what is the blocking size that amanda uses? Don't know. 2) If anyone here is using an sdx-500 AIT-2 tape drive, what are your dip switches set to? (I'm wondering if I need to enable variable block sizing on the drive). On my SDX-500 AIT-2 drives, I have 1-7 off and 8 on. The documentation says switches 1-4 6 are reserved and should be off, 5 is termination power, 7 is HW compression (0-off,1-on), and 8 is SW compression control (0 lets host enable/disable compression, 1 disables host control). I think the default is 0-6 off, 7 on , 8 off. The manual says it is capable of either fixed or variable block sizes, it doesn't mention anything about enabling/disabling it in hardware; it should be up to the driver. 3) Has anyone else using an AIT tape drive had similar problems? Not me. Did this problem recently start or have you never used it before? Are the tapes new or old? What is the exact error you're getting? Can you tar or dump directly to and from the tape without errors? OS and version? Frank Thanks -Rob -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: AIT-2
Dege, Robert C. wrote: I'm currently having problems restoring files from my amanda backup system. I am able to narrow the problem down to my AIT-2 tape drive. If I restore files from amanda backups that are still on the holding disk, I have a successful restore. If I restore files from any of the AIT-2 tapes, I get tar errors. What kind of tar errors? So I have a few questions: 1) When amanda uses tar to backup the data, what is the blocking size that amanda uses? Default blocksize is 32Kbytes, but can be configured when compiling amanda, and on the settings of the hardware. 2) If anyone here is using an sdx-500 AIT-2 tape drive, what are your dip switches set to? (I'm wondering if I need to enable variable block sizing on the drive). Variable blocksize is necessary to get the 32K blocks that amanda tries to use. If you have a fixed blocked size of e.g. 512 bytes, then no matter the blocksize amanda writes, it will be chunked up in 512 bytes on tape (and that very very slow). 3) Has anyone else using an AIT tape drive had similar problems? I am a satisfied user of AIT-1 for more than 3 years now. I had no problems, nor did I need to change the dipswitches from the factory defaults. A lot of settings depend on the OS where the tapedrive is connected to. And of course the quality of the scsi-link (good cables? good terminated?) -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: AIT-2
On Wed, Apr 07, 2004 at 11:25:10AM -0700, Dege, Robert C. wrote: Hi, I'm currently having problems restoring files from my amanda backup system. I am able to narrow the problem down to my AIT-2 tape drive. If I restore files from amanda backups that are still on the holding disk, I have a successful restore. If I restore files from any of the AIT-2 tapes, I get tar errors. what platform/OS is your tapehost? So I have a few questions: 1) When amanda uses tar to backup the data, what is the blocking size that amanda uses? no idea. 2) If anyone here is using an sdx-500 AIT-2 tape drive, what are your dip switches set to? (I'm wondering if I need to enable variable block sizing on the drive). from the Fine Manual: O O O O O O I O 1 2 3 4 5 6 7 8 did you also modify your SCSI tape driver config file (/kernel/drv/st.conf on Solaris) so the driver can know about particular capabilities of the tapedrive? these tips can be found in: http://www.sony.jp/products/Professional/DataArchive/pdf/unix216.pdf 3) Has anyone else using an AIT tape drive had similar problems? only with larger tape files, e.g. over ~16Gb in size. symptom was device timeouts on the tape device, and amanda thought these dumps were successful! Thanks -Rob chris -- Christopher Linn, (celinn at mtu.edu) | By no means shall either the CEC Staff System Administrator| or MTU be held in any way liable Center for Experimental Computation | for any opinions or conjecture I Michigan Technological University | hold to or imply to hold herein.
RE: AIT-2
On my SDX-500 AIT-2 drives, I have 1-7 off and 8 on. The documentation says switches 1-4 6 are reserved and should be off, 5 is termination power, 7 is HW compression (0-off,1-on), and 8 is SW compression control (0 lets host enable/disable compression, 1 disables host control). I think the default is 0-6 off, 7 on , 8 off. The manual says it is capable of either fixed or variable block sizes, it doesn't mention anything about enabling/disabling it in hardware; it should be up to the driver. Thanks for the detailed info about the dip switches. My manual lists all but DIP #7 as reserved. 3) Has anyone else using an AIT tape drive had similar problems? Not me. Did this problem recently start or have you never used it before? Are the tapes new or old? What is the exact error you're getting? Can you tar or dump directly to and from the tape without errors? OS and version? This problem existed ever since I tried to do my first resetore from tape. All of the tapes are less than 4 months old. I receive 2 error messages. When using amrecover, I receive an error message to stdout as follows: Extracting files using tape drive /dev/nst0 on host bender. Load tape BACKUP-22 now Continue [?/Y/n/s/t]? y snip as restore begins ./r50/bin/MSFD_UTILITY.EXE ./r50/bin/PDM_SIMULATION_APPLICATION.EXE ./r50/bin/PGS_CRITERIA_VALIDATOR_DRIVER.EXE tar: Skipping to next header tar: Archive contains obsolescent base-64 headers tar: Error exit delayed from previous errors extract_list - child returned non-zero status: 2 Continue [?/Y/n/r]? y amrecover exit 200 Good bye. The other message occurs in /tmp/amanda/amidxtaped debug file: amrestore: 8: restoring bender._rfss_ceesim_8k_lib-r50s.20040326.0 gzip: stdin: invalid compressed data--crc error gzip: stdin: invalid compressed data--length error amrestore: 9: reached end of information amidxtaped: time 294.174: amrestore terminated normally with status: 1 amidxtaped: time 294.174: rewinding tape ... amidxtaped: time 341.208: done amidxtaped: time 341.208: pid 25238 finish time Tue Apr 6 10:26:33 2004 -Rob
RE: AIT-2
--On Wednesday, April 07, 2004 13:08:10 -0700 Dege, Robert C. [EMAIL PROTECTED] wrote: On my SDX-500 AIT-2 drives, I have 1-7 off and 8 on. The documentation says switches 1-4 6 are reserved and should be off, 5 is termination power, 7 is HW compression (0-off,1-on), and 8 is SW compression control (0 lets host enable/disable compression, 1 disables host control). I think the default is 0-6 off, 7 on , 8 off. The manual says it is capable of either fixed or variable block sizes, it doesn't mention anything about enabling/disabling it in hardware; it should be up to the driver. Thanks for the detailed info about the dip switches. My manual lists all but DIP #7 as reserved. 3) Has anyone else using an AIT tape drive had similar problems? Not me. Did this problem recently start or have you never used it before? Are the tapes new or old? What is the exact error you're getting? Can you tar or dump directly to and from the tape without errors? OS and version? This problem existed ever since I tried to do my first resetore from tape. All of the tapes are less than 4 months old. I receive 2 error messages. When using amrecover, I receive an error message to stdout as follows: Extracting files using tape drive /dev/nst0 on host bender. Load tape BACKUP-22 now Continue [?/Y/n/s/t]? y snip as restore begins ./r50/bin/MSFD_UTILITY.EXE ./r50/bin/PDM_SIMULATION_APPLICATION.EXE ./r50/bin/PGS_CRITERIA_VALIDATOR_DRIVER.EXE tar: Skipping to next header tar: Archive contains obsolescent base-64 headers tar: Error exit delayed from previous errors extract_list - child returned non-zero status: 2 Continue [?/Y/n/r]? y amrecover exit 200 Good bye. Are you recovering on the client or the server? Are you recovering from more than one DLE? Perhaps the data was compressed on a box using a compression program not available on the box doing the recover. Frank The other message occurs in /tmp/amanda/amidxtaped debug file: amrestore: 8: restoring bender._rfss_ceesim_8k_lib-r50s.20040326.0 gzip: stdin: invalid compressed data--crc error gzip: stdin: invalid compressed data--length error amrestore: 9: reached end of information amidxtaped: time 294.174: amrestore terminated normally with status: 1 amidxtaped: time 294.174: rewinding tape ... amidxtaped: time 341.208: done amidxtaped: time 341.208: pid 25238 finish time Tue Apr 6 10:26:33 2004 -Rob -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
RE: AIT-2
what platform/OS is your tapehost? AMD System, running RedHat 9.0. I'm using a stock 2.4.22 kernel. did you also modify your SCSI tape driver config file (/kernel/drv/st.conf on Solaris) so the driver can know about particular capabilities of the tapedrive? I didn't modify any kernel source files. I'm using 2 modules, st.o for the tape drive, and sg.o for the tape changer. only with larger tape files, e.g. over ~16Gb in size. symptom was device timeouts on the tape device, and amanda thought these dumps were successful! Really? How were you able to resolve this problem? Did you lower chunksize or something similar in the amanda.conf file? -Rob
RE: AIT-2
Are you recovering on the client or the server? Are you recovering from more than one DLE? Perhaps the data was compressed on a box using a compression program not available on the box doing the recover. Frank The system is both the client the server. I checked the config file in the source code, and verified that amanda is using /bin/gzip, and /bin/gtar. Right now, I'm only trying to restore from a single DLE. One thing that I did notice is that I built amanda using additional CFLAGS. Do you these extra optimizations might be causing the problem? (This is one of those out field kind of questions) -Rob
RE: AIT-2
Jay, thanks for all this info. I am able to run these dd commands successfully. So I'm beginning to think that amanda is the source of the problem. However, before I go any further, I'm extracting the data from the tapeimages to ensure that tar doesn't crash. -Rob -Original Message- From: Jay Fenlason [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 5:20 PM To: Dege, Robert C. Subject: Re: AIT-2 On Wed, Apr 07, 2004 at 01:23:53PM -0700, Dege, Robert C. wrote: Can you take one of your backup tapes and access the files on it reliably with dd? If you can't, it's likely to be a hardware/os/etc problem. If you can, it may be an Amanda problem. Is there any chane of bad termination on your SCSI chain? What would the dd command line be? Start with the tape rewound. cd to a directory with a lot of space. (Up to 50Gb if you want to read your entire AIT-2 tape.) dd /dev/nst0 tapeimage.1 bs=32k dd /dev/nst0 tapeimage.2 bs=32k dd /dev/nst0 tapeimage.3 bs=32k dd /dev/nst0 tapeimage.4 bs=32k dd /dev/nst0 tapeimage.5 bs=32k dd /dev/nst0 tapeimage.6 bs=32k ... (Repeat the dd command until it creates an empty file.) The first tapeimage file will be the Amanda tape label. The last file with data in it will be the Amanda tape end marker. The other files will be the backups. If dd read all the backups and the end marker successfully, any remaining problem is likely to be Amanda's. Each of the backups is going to be a (possibly compressed) dump output file or a (possibly compressed) tar file. Either way, there's a 32k header that you need to skip over to get at the actual data. If they're tar files, you should be able to read them with dd tapeimage.n bs=32k skip=1 | gtar tvf - If they're compressed tar files, you'll need dd tapeimage.n bs=32k skip=1 | gunzip | gtar tvf - If they're dump files, I don't know how to read them. Check the restore man page. Right now, I'm running a tar command directly to a standard AIT-2 tape. I want to see if the problem is with tar, or with amanda using tar. I'm tarring files to the tape, and then will try to extract the files. I'm also using the same file chunk that failed on amanda to eliminate any additional variables in my test. I don't think SCSI termination is the problem since I can use the tape changer without any problems, and backups occur without error on a nightly basis. I'll double-check tough. If it's a hardware or OS problem, your tar test should find it. -- JF
Re: AIT-2
On Wed, Apr 07, 2004 at 01:51:08PM -0700, Dege, Robert C. wrote: what platform/OS is your tapehost? AMD System, running RedHat 9.0. I'm using a stock 2.4.22 kernel. OK. i've never run a linux amanda server/tapehost. did you also modify your SCSI tape driver config file (/kernel/drv/st.conf on Solaris) so the driver can know about particular capabilities of the tapedrive? I didn't modify any kernel source files. I'm using 2 modules, st.o for the tape drive, and sg.o for the tape changer. i don't know how the linux kernel does this. i hear tell of a SCSI HowTo out there, maybe even a SCSI Tape HowTo.. only with larger tape files, e.g. over ~16Gb in size. symptom was device timeouts on the tape device, and amanda thought these dumps were successful! Really? How were you able to resolve this problem? Did you lower chunksize or something similar in the amanda.conf file? i put the DIP switches the way they were supposed to be, and added the relevant lines to the (solaris) st.conf file.. ;*) i am suspicious that the st.conf definitions were key. kernel debug logging stopped showing the device timeouts. -Rob chris -- Christopher Linn, (celinn at mtu.edu) | By no means shall either the CEC Staff System Administrator| or MTU be held in any way liable Center for Experimental Computation | for any opinions or conjecture I Michigan Technological University | hold to or imply to hold herein.
Re: AIT-2
On Wed, Apr 07, 2004 at 02:44:10PM -0700, Dege, Robert C. wrote: thanks for all this info. I am able to run these dd commands successfully. So I'm beginning to think that amanda is the source of the problem. Here's a stab-in-the-dark sort of guess: maybe amrecover is using a different gtar than amdump did, and the former can't read the latter's tarballs. This: tar: Archive contains obsolescent base-64 headers suggests a format incompatibility rather than data corruption (though of course, if the latter were just so, it could masquerade as the former). If you have an strace, trace, or truss command (they're all pretty much equivalent), it can help you determine this. Which gtar version? 1.13 is known not to work with Amanda (though the typical symptoms are different from yours); 1.13.25, from alpha.gnu.org, is recommended. (There are later versions, 1.13.9x, but I've seen those recommended *against* on this list. I don't know whether that's because they're known to be broken, or simply not yet known to be reliable.) Another thing to try would be amrestore (as opposed to amrecover). That pulls backup images off the tape, and optionally decompresses them, but does *not* try to untar them. Thus, it would help you to narrow down the problem. I *think* the command would be something like this (I use it rarely enough that I always have to try a few times to get it right): $ amrestore [-r] /dev/nst0 hostname DLEname That will search the tape for the backup of (hostname,DLEname), pull the entire backup image off the tape, and store it in the current directory. With -r, it will store exactly what this dd command of Jay's would have stored: dd /dev/nst0 tapeimage.1 bs=32k Without -r, it will strip off the 32-KB header and decompress the rest, rather like this dd command: dd tapeimage.n bs=32k skip=1 | gunzip (this is one of Jay's commands too, except that the original had | gtar tvf - appended). So try this to narrow it down: 1. pick a restore that you've seen fail 2. use dd and see if that can pull the file off the tape without errors (you've already done this) 3. use amrestore -r and see if the output is identical to that of (2) 4. manually header-strip and decompress the result of (2), using the second dd command above 5. use amrestore with no -r, and see if its output is identical to the output of (4) 6. For paranoia's sake, try again the same amrecover command that failed before. Unless it fails with the *identical* message (except for timestamps, process IDs, and the like), and produces *identical* partial restore output, strongly suspect hardware problems -- | | /\ |-_|/ Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / It must be said that they would have sounded better if the singer wouldn't throw his fellow band members to the ground and toss the drum kit around during songs. - Patrick Lenneau
The find right tape function is now broken
IF the right tape is already loaded. Sounds weird, but its true. Now, I'm going to back up one amanda snapshot at a time and see if I can find what snapshot broke it. Basicly, if the tape it wants is in fact loaded into the drive, then amcheck nor amdump ( probably amflush too) cannot find it. Here is the mail from an amcheck run at 4pm, and I had the correct tape for tonight already loaded when cron ran amcheck again, returning this: Amanda Tape Server Host Check - Holding disk /dumps: 17515496 KB disk space available, using 17003496 KB amcheck-server: slot 3: tape_rdlabel: tape open: /dev/nst0: Input/output error amcheck-server: slot 0: date 20040405 label DailySet1-10 (active tape) amcheck-server: slot 1: date 20040406 label DailySet1-11 (active tape) amcheck-server: slot 2: date 20040407 label DailySet1-12 (active tape) ERROR: label DailySet1-13 or new tape not found in rack (expecting tape DailySet1-13 or a new tape) NOTE: skipping tape-writable test Server check took 404.023 seconds Amanda Backup Client Hosts Check Client check: 2 hosts checked in 0.529 seconds, 0 problems found (brought to you by Amanda 2.4.5b1-20040406) So, I rerun amcheck, it finds the tape in slot 3 just like its supposed to. Curious george here smells a rat, so I reran it twice more, getting this: [EMAIL PROTECTED] amanda-2.4.5b1-20040406]$ amcheck DailySet1 Amanda Tape Server Host Check - Holding disk /dumps: 17515108 KB disk space available, using 17003108 KB amcheck-server: slot 3: tape_rdlabel: tape open: /dev/nst0: Input/output error amcheck-server: slot 0: date 20040405 label DailySet1-10 (active tape) amcheck-server: slot 1: date 20040406 label DailySet1-11 (active tape) amcheck-server: slot 2: date 20040407 label DailySet1-12 (active tape) ERROR: label DailySet1-13 or new tape not found in rack (expecting tape DailySet1-13 or a new tape) NOTE: skipping tape-writable test Server check took 376.261 seconds Amanda Backup Client Hosts Check Client check: 2 hosts checked in 0.188 seconds, 0 problems found (brought to you by Amanda 2.4.5b1-20040406) [EMAIL PROTECTED] amanda-2.4.5b1-20040406]$ amcheck DailySet1 Amanda Tape Server Host Check - Holding disk /dumps: 17514916 KB disk space available, using 17002916 KB amcheck-server: slot 2: date 20040407 label DailySet1-12 (active tape) amcheck-server: slot 3: date 20040111 label DailySet1-13 (exact label match) NOTE: skipping tape-writable test Tape DailySet1-13 label ok Server check took 118.713 seconds Amanda Backup Client Hosts Check Client check: 2 hosts checked in 0.208 seconds, 0 problems found (brought to you by Amanda 2.4.5b1-20040406) [EMAIL PROTECTED] amanda-2.4.5b1-20040406] I can repeat this till I've worn out the tapes it appears. Next, since I've got these src dirs with amanda already built: amanda-2.4.4p2-20040129 amanda-2.4.5b1-20040323.tar.gz amanda-2.4.4p2-20040129.tar.gz amanda-2.4.5b1-20040326 amanda-2.4.5b1-20040202 amanda-2.4.5b1-20040326.tar.gz amanda-2.4.5b1-20040202.tar.gz amanda-2.4.5b1-20040405 amanda-2.4.5b1-20040213 amanda-2.4.5b1-20040405.tar.gz amanda-2.4.5b1-20040213.tar.gz amanda-2.4.5b1-20040406 amanda-2.4.5b1-20040316 amanda-2.4.5b1-20040406.tar.gz amanda-2.4.5b1-20040316.tar.gz amanda-2.4.5b1-20040319.tar.gz amanda-2.4.5b1-20040323 I'm going to reinstall older ones till it works. Starting with 0316. That failed, then I have a gap as I was out of town, so the next one back is 0213, and it also failed. Next back is 0202. And that one failed to read the tape already left loaded by a previous run. Now to try 2.4.4p2-20040129... And it also fails thats as far back as I can go with whats on hand. I'm seeing a pattern here, but its spotty. Going back to the latest snapshot for now, and to play with the chg-scsi.conf sleep time value, currently at 20 seconds, tried 60 which appears to be a total failure. Been using 30 for years. This was being a problem before I put in the newer changer, but I was blaming the changer then because a cleaning tape run would fix it for a short time. This one is not telling me its dirty by way of the front panel. This is enough for one night, any ideas from anyone, or some help from Thomas Hepper, who was the last to walk around in that code that I know of, would be nice. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) 99.22% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
