Tape Open, Input/Output Error
I'm still pretty new to Linux and Amanda. I'm receiving the following error during amcheck: Amanda Tape Server Host Check - WARNING: holding disk /opt/amanda: only 15564476 KB free, using nothing ERROR: /dev/nst0: tape_rdlabel: tape open: /dev/nst0: Input/output error (expecting tape Daily-002 or a new tape) NOTE: skipping tape-writable test Server check took 0.648 seconds Amanda Backup Client Hosts Check Client check: 3 hosts checked in 16.401 seconds, 0 problems found (brought to you by Amanda 2.4.4p1) Recommendations on best way to proceed? Thanx in advance. -- View this message in context: http://www.nabble.com/Tape-Open%2C-Input-Output-Error-tp16197933p16197933.html Sent from the Amanda - Users mailing list archive at Nabble.com.
Re: Tape Open, Input/Output Error
On Fri, Mar 21, 2008 at 06:57:28AM -0700, Tom Herrera wrote: I'm still pretty new to Linux and Amanda. I'm receiving the following error during amcheck: Amanda Tape Server Host Check - WARNING: holding disk /opt/amanda: only 15564476 KB free, using nothing ERROR: /dev/nst0: tape_rdlabel: tape open: /dev/nst0: Input/output error (expecting tape Daily-002 or a new tape) NOTE: skipping tape-writable test Server check took 0.648 seconds Amanda Backup Client Hosts Check Client check: 3 hosts checked in 16.401 seconds, 0 problems found (brought to you by Amanda 2.4.4p1) Recommendations on best way to proceed? Thanx in advance. I'd start by mimicing amanda's actions manually to narrow where to look. Can you manually read the tape label as the amanda user id? Something like this: $ su - amanda_user ... $ dd if=/dev/nst0 bs=32k count=1 The label is text and you should see it on-screen. jl -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 12027 Creekbend Drive (703) 787-0884 Reston, VA 20194 (703) 787-0922 (fax)
Re: Tape Open, Input/Output Error
Amanda Tape Server Host Check - WARNING: holding disk /opt/amanda: only 15564476 KB free, using nothing ERROR: /dev/nst0: tape_rdlabel: tape open: /dev/nst0: Input/output error (expecting tape Daily-002 or a new tape) use mt -f /dev/nst0 status to see if it shows anything, it might be the tape door is not closed. And check dmesg output, see if any tape related error. NOTE: skipping tape-writable test Server check took 0.648 seconds Amanda Backup Client Hosts Check Client check: 3 hosts checked in 16.401 seconds, 0 problems found (brought to you by Amanda 2.4.4p1) Recommendations on best way to proceed? Thanx in advance. === Yu Chen Howard Hughes Medical Institute Chemistry Building, Rm 182 University of Maryland at Baltimore County 1000 Hilltop Circle Baltimore, MD 21250 phone: (410)455-1728 (primary) (410)455-6347 (secondary) fax:(410)455-1174 email: [EMAIL PROTECTED] ===
Re: amanda dumps on Sun E250
** email thread greatly trimmed ** Chris, amDump time changed from 48 hours to 14 hours On Tue, Mar 18, 2008 at 06:29:46PM -0400, Chris Hoogendyk wrote: Interesting that your LTO3 is doing no better than your LTO for speed. I would guess you should be getting 3 times the speed you are getting on LTO and well over 10 times the speed you are getting on LTO3. It is curious, and indicated something common as the problem since the drives are on separate bussed, the LTO being on a DIFF bus and the LTO3 and multipack with the holding area (multiple spindles) being on their own ports on an HBA that provides LVD/SE. We are not using the standard SCSI port (meantioned later in this email). Did a little looking in the HW manual and the online version of the handbook, the PCI slots are not all created equally. The top of the 4 slots will run at either 66 or 33 Mhz, the lower three slots will run only at 33 Mhz. We removed the now unused fiber HBA (no longer connected to massive storage since we migrated the Lotus Notes function to the newer T2000 system) and moved the LVD/SE HBA to the higher speed slot. This largely if not completely solves the problems, I will provide amdump output later in the email. Also, doing hardware compression, I would expect you to get more than you are on tape unless the data is relatively uncompressable. If Lotus keeps its stuff in compressed form, you could be running into slowdowns on the hardware compression. I had thought of that also. We are using the Ultra device name which should select (when there is an option) highest density and compression. The tapes where labeled using that device, I think if that failed then we'd have a tape being written without compression and would already be avoiding the issues you suggest. With the speeds you are getting, I would be worried about shoe shining. Can you actually watch the tapes while they are running and see what's happening? That will take a slow speed and make it dismal, which is what you have. My AIT5 on my E250 is beating out your LTO3, and it shouldn't. You should be 2-3 times faster. Unfortunately with the drives being imbedded in respective their libraries there is no direct way for me to know if they are shoe shining, almost makes one wish for a nice standup, glass fronted 9 track tape so we could see what was going on. Maybe someone will start to build tapes with some additional indicated LEDs on them. If any of that makes sense to you, and since you don't seem to be gaining much from compression, I'd be inclined to turn off compression altogether and see what happens. Of course, that can be a bit tricky with tapes that have already been used with compression. I think I saw a discussion somewhere about someone turning backflips to accomplish that. Might have been on the bacula list. Tape drives and OS level stuff translate almost completely between the two lists. If you can ever get any down time, I would be inclined to take one of the large notes partitions, recover it to the holding disk, and then play with dd'ing it to the tape until you figure out what's up. One of the great values of having the amanda server separate from the LNotes server is downtime. Fortunately I was able to juggle the HBAs to new slots without interupting end-user services. If you use the standard SCSI port on the back of the E250, it is UltraSCSI, but only the earliest version. It can only do 40MB/s. It also supports single ended, wide or narrow SCSI devices. So, if there are other things also connected, and you are using that connection, then you probably have a problem with LTO3 from that perspective. I would double check and make sure you have connections and adapters that will support the throughput you need. I presume you have the E250 Server Owner's Guide? You hit the nail on the head there. Good luck (intended positively ;-) ). I see a great level of improvement, not only in the holding-area to tape time but in the dump performance to the holding-area. We also never filled the holding area, since we had free space as data was able to get to tape we had greater concurrently as well as the dumps being faster, presumably because the I/O to and from the holding area was faster, as well as tape I/O being faster. I do not know if we did much to improve the I/O to the LTO tape, which we only run on weekends, having better holding area I/O will certainly help, but there are no more fast PCI slots available and the LTO is on the DIFF bus in the 33Mhz slot. We will know more on Monday, or if it runs like it did last weekend on Tuesday, not great for a weekly Saturday amdump. These where the stats when the HBA was in its original position, the slower 33 Mhz PCI slot. Thank you for your help - and I will try to review and perhaps change the compression settings on the LTO drive, though some of these partitions will not fit on the tape unless compressed.
Re: Tape Open, Input/Output Error
I'm still pretty new to Linux and Amanda. I'm receiving the following error during amcheck: Amanda Tape Server Host Check - WARNING: holding disk /opt/amanda: only 15564476 KB free, using nothing ERROR: /dev/nst0: tape_rdlabel: tape open: /dev/nst0: Input/output error (expecting tape Daily-002 or a new tape) NOTE: skipping tape-writable test Server check took 0.648 seconds Amanda Backup Client Hosts Check Client check: 3 hosts checked in 16.401 seconds, 0 problems found (brought to you by Amanda 2.4.4p1) Recommendations on best way to proceed? Thanx in advance. Jon Labadie wrote: I'd start by mimicing amanda's actions manually to narrow where to look. Can you manually read the tape label as the amanda user id? Something like this: $ su - amanda_user ... $ dd if=/dev/nst0 bs=32k count=1 The label is text and you should see it on-screen. I may have fixed the issue by physical means. I ejected the tape, turned the drive off and on, used a cleaning tape, then reinserted the tape. amcheck now reports all is well, but I'm, well, a little concerned. When I run dd if=/dev/nst0 bs=32k count=1 the response is: 0+0 records in 0+0 records out When I run amflush Daily the response is: Scanning /opt/amanda... Today is: 20080321 Flushing dumps in to tape drive /dev/nst0. Expecting tape Daily-002 or a new tape. (The last dumps were to tape Daily-001) Are you sure you want to do this [yN]? N Ok, quitting. Run amflush again when you are ready. As you can see, there is no text label using the dd command, and I would think there ought to be something to flush, since the amreport was screaming: *** A TAPE ERROR OCCURRED: [tape_rdlabel: tape open: /dev/nst0: Input/output error]. Some dumps may have been left in the holding disk. Run amflush to flush them to tape. The next tape Amanda expects to use is: Daily-002. FAILURE AND STRANGE DUMP SUMMARY: madison.ch //accounting/Apps lev 1 FAILED [no more holding disk space] madison.ch /opt lev 2 FAILED [can't dump no-hold disk in degraded mode] madison.ch /boot lev 1 FAILED [no more holding disk space] nostep.chi /boot lev 1 FAILED [no more holding disk space] tyler.chi. /var lev 1 FAILED [no more holding disk space] tyler.chi. /export lev 1 FAILED [no more holding disk space] tyler.chi. /opt lev 1 FAILED [no more holding disk space] madison.ch /var lev 1 FAILED [no more holding disk space] madison.ch /export/home lev 1 FAILED [no more holding disk space] madison.ch //accounting/Finance lev 1 FAILED [no more holding disk space] tyler.chi. / lev 1 FAILED [no more holding disk space] tyler.chi. /boot lev 1 FAILED [no more holding disk space] madison.ch / lev 1 FAILED [no more holding disk space] nostep.chi / lev 1 FAILED [no more holding disk space] It doesn't look like I need to run amflush, or should I anyway? Is all of this an indication that there may be something wrong with either the tape or drive? Or should I just skip over my twitch of paranoia and move on? Thanx.
doing ssh backups of clients listening on non-standard ssh ports
For supposed security reasons, some of our servers have ssh listening on a different port. Has anyone done ssh authenticated backups of servers listening on a port other than 22? I haven't seen where you can configure any ssh related options for these types of backups. This would be run on linux and freebsd machines running amanda 2.5.2p1. Any information would be appreciated.
Re: doing ssh backups of clients listening on non-standard ssh ports
Nomad [EMAIL PROTECTED] (Fr 21 Mär 2008 22:23:08 CET): For supposed security reasons, some of our servers have ssh listening on a different port. Has anyone done ssh authenticated backups of servers listening on a port other than 22? I haven't seen where you can configure any ssh related options for these types of backups. This would be run on linux and freebsd machines running amanda 2.5.2p1. I've never done ssh based amanda backups. If it uses the OpenSSH client, it should read $HOME/.ssh/config. There proably you can put your options like: Host bigiron Port 4711 Best regards from Dresden Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de internet unix support - Heiko Schlittermann HS12-RIPE - gnupg encrypted messages are welcome - key ID: 48D0359B --- gnupg fingerprint: 3061 CFBF 2D88 F034 E8D2 7E92 EE4E AC98 48D0 359B - signature.asc Description: Digital signature
Re: doing ssh backups of clients listening on non-standard ssh ports
Heiko Schlittermann wrote: Nomad [EMAIL PROTECTED] (Fr 21 Mär 2008 22:23:08 CET): For supposed security reasons, some of our servers have ssh listening on a different port. Has anyone done ssh authenticated backups of servers listening on a port other than 22? I haven't seen where you can configure any ssh related options for these types of backups. This would be run on linux and freebsd machines running amanda 2.5.2p1. I've never done ssh based amanda backups. If it uses the OpenSSH client, it should read $HOME/.ssh/config. There proably you can put your options like: Host bigiron Port 4711 I do use ssh. The solution above is correct and is spelled out here: http://wiki.zmanda.com/index.php/How_To:Set_up_transport_encryption_with_SSH#Non-Standard_SSH_Port --- Chris Hoogendyk - O__ Systems Administrator c/ /'_ --- Biology Geology Departments (*) \(*) -- 140 Morrill Science Center ~~ - University of Massachusetts, Amherst [EMAIL PROTECTED] --- Erdös 4
error compiling amanda on FreeBSD 6.3 x86_64
I'm attempting to compile the client version of amanda on a Dell PowerEdge
server running FreeBSD 6.3 but keep running into an ssh related error. I use
the following configure statement:
./configure --prefix=/usr/local/amanda25 --infodir=/usr/share/info
--mandir=/usr/share/man --with-user=amanda --with-group=operator
--with-config=daily --with-gnutar=/usr/local/bin/amgtar
--with-gnutar-listdir=/usr/local/amanda25/gnutar-lists --with-debugging
--with-debug-days=21 --with-fqdn --with-ssh-security --with-buffered-dump
--with-dump-honor-nodump --without-server
--with-tape-server=amandaserver.utexas.edu --with-tmpdir=/tmp/amanda
--with-index-server=amandaserver.utexas.edu
but eventually I get this error:
checking build system type... x86_64-unknown-freebsd6.3
checking host system type... x86_64-unknown-freebsd6.3
checking target system type... x86_64-unknown-freebsd6.3
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
..
checking for egrep... /usr/bin/egrep
checking for lint... /usr/bin/lint
lint: illegal option -- f
usage: lint [-abceghprvwxzHF] [-s|-t] [-i|-nu] [-Dname[=def]] [-Uname] [-X
id[,id]...
[-Idirectory] [-Ldirectory] [-llibrary] [-ooutputfile] file...
lint [-abceghprvwzHF] [-s|-t] -Clibrary [-Dname[=def]]
[-X id[,id]...
[-Idirectory] [-Uname] [-Bpath] file ...
checking for raw ftape device... /dev/null
checking for Kerberos and Amanda kerberos4 bits... no
checking for ssh... /usr/bin/ssh
checking SSH options... ./configure.lineno: ${i/...}: Bad substitution
(ignore the lint related error) If I take out the --with-ssh-security, amanda
configures without a problem. Here's some of the output from /var/run/dmesg.boot:
Copyright (c) 1992-2008 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 6.3-RELEASE #0: Wed Jan 16 01:43:02 UTC 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP
ACPI APIC Table: DELL PE_SC3
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: Intel(R) Xeon(R) CPU X5355 @ 2.66GHz (2662.67-MHz K8-class CPU)
Origin = GenuineIntel Id = 0x6f7 Stepping = 7
Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE
Features2=0x4e3bdSSE3,RSVD2,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA
AMD Features=0x20100800SYSCALL,NX,LM
AMD Features2=0x1LAHF
Cores per package: 4
real memory = 9395240960 (8960 MB)
avail memory = 8290398208 (7906 MB)
FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs
Any thoughts/suggestions?
Oscar
