Date: Sat, 2 Nov 2002 12:52:05 +0100 (CET) From: "Hartmann, O." <ohartman@klima.physik.uni-mainz.de> To: arc@tradewindse.com Cc: freebsd-stable@freebsd.org, <freebsd-questions@freebsd.org> Subject: Re: afbackup anybody know what these errors mean? (fwd) Message-ID: <20021102123039.X26303-100000@klima.physik.uni-mainz.de> In-Reply-To: <20021102122941.S26183-100000@klima.physik.uni-mainz.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello.
Yes, I saw and still see this obscure message since August 2002!
I did several postings here and got into contact with A. Fluegel,
one of the vendors of afbackup.
Afbackup worked 'stable' until we changed from FreeBSD 4.6.2 to 4.6.2-pl2
and this error occurs on our HP SureStore 40x6i DAT changer. The server
which is doing the update needs to backup about 250GB diskspace and
therefore we bought this poor-man's tape changer. Prior to this change
to FreeBSD 4.6.2-pl2 and FreeBSD 4.7-R and followers every version of afbackup
until version 3.3.7 worked like a charm. The several weird errors occured,
first time error was an error when really big files were written and read again
from backup, but Alber Fluegel told me that this has been worked around. The
more critical problem is that what you mentioned here: at the end of a tape
we get this error and afbackup dies. This only happens on our changer.
We run also two other HP backup devices, one DAT 40 single drive and an older
DAT 8 drive and in addtion a sony DAT 7000 drive. The older DAT drives (single)
have no problems in FreeBSD 4.7-R and afbackup 3.3.7pl3, but the important
changer device seems to make trouble in afbackup.
I tried to do several poor investigations on this to exclude the drive's fault.
Using pax or tar in multivolume mode shows no error when tape end has been reached,
but after the change of the cartridge magazine (6 tapes) pax get confused and
whenever a new tape is inserted, it reports a full volume. I never saw this before
in 4.6 but I can not assure this is a new 'bug' in 4.7.
The only thing I know is that with the 2nd August 2002 something has been changed
in scsi_sa.c and this caused a thread I read in GOOGLE concerning some changes in
EOT handling (look for posting of Matthew Jacob). Since August we have this massive
trouble although our error looks like a little bit different from yours (error number
is 87 or 85 and command is not '>', it is 'W', but the error message behind the cause
is the same).
Do you have a changer, too, or occurs this error on a single tape drive?
Well, as I understood the above mentioned thread about EOT handling, in afbackup we
got several changes targeting this but as I understood Mr. Jacob the right way, he
changed back EOT bahaviour.
I hope these problems get fixed soon. afbackup was the only non commercial backup
software for FreeBSD which is able to backup large disk arrays (AMANDA is a crap,
using tar and is not able to split large files/arrays over several consecutive
tapes).
If you get some more informations about this, I would appreciate any comments or
tips.
Our backup system is a FreeBSD 4.7-R-p1 SMP box, HP SureSTore 40x6i tape drive/changer
unit attached to an onboard LSI Logic 53C896 LVD SCSI host controler on a TYAN Thunder
2500 mainboard. The tape drive unit populate one of two channels as the only device,
so bad interaction with other devices should be excluded.
:>---------- Forwarded message ----------
:>Date: Thu, 31 Oct 2002 11:41:54 -0500
:>From: Arley Carter <arc@tradewindse.com>
:>To: freebsd-stable@FreeBSD.ORG
:>Subject: afbackup anybody know what these errors mean?
:>
:>I am receiving these errors below when a client tries to back up to a
:>server.
:>
:>#./full-backup
:>
:>In the client log:
:>Thu Oct 31 09:35:31 2002, Starting full backup.
:>Thu Oct 31 09:41:53 2002, Error: Backup client side did not receive
:>necessary starting information from server. Output was:.
:>Thu Oct 31 09:41:53 2002, Streamer state: READY
:>Server-ID: hatteras:/usr/local/afbackup/server/etc
:>Precious tapes: -
:>.
:>Thu Oct 31 09:41:53 2002, Full backup failed.
:>
:>The server log says
:>
:>Thu Oct 31 09:41:07 2002, Warning: Setting the file number 50 failed.
:>Thu Oct 31 09:41:07 2002, Error: Command 62 ('>') failed (cannot open device
:>for writing)
:>
:>However when I query the tape drive on the server I get:
:>
:>laser# /usr/local/afbackup/client/bin/afclient -qwv -h hatteras
:>
:>Streamer state: READY
:>Server-ID: hatteras:/usr/local/afbackup/server/etc
:>Precious tapes: -
:>Current tape access position
:>Cartridge: 1
:>File: 1
:>Number of cartridges: 1
:>Current cartridge set: 1
:>
:>Also pref-client on the server says:
:>
:>laser.marine.tradewindse.com 1036080814 <client-program>
:>
:>And server-ids on the client says:
:>
:>hatteras 2988 hatteras:/usr/local/afbackup/server/etc
:>
:>So, obviously the client and server can find and recognize each other and
:>the client can find the tape drive.
:>
:>Anybody know how to decrypt these error messages to find the cause of why
:>the tape is not starting? The tape light comes on and the tape moves, so
:>the tape is being accessed. Apparently though the tape isn't being opened
:>for wrting.
:>
:>Hardware and software :
:>Server: Sun Ultra 5 , Solaris 8. Tape Drive Hp1553 4 mm DAT ,
:>client: freebsd4-7-Release
:>afbackup software version: 3.3.7p13
:>
:>Anybody have any ideas or seen something like this before?
:>
:>Arley Carter
:>Tradewinds Technologies, Inc. arc@tradewindse.com
:>Charlotte, NC USA www.tradewindse.com
:>
:>
:>
:>
:>
:>To Unsubscribe: send mail to majordomo@FreeBSD.org
:>with "unsubscribe freebsd-stable" in the body of the message
:>
:>
--
MfG
O. Hartmann
ohartman@klima.physik.uni-mainz.de
------------------------------------------------------------------
IT-Administration des Institutes fuer Physik der Atmosphaere (IPA)
------------------------------------------------------------------
Johannes Gutenberg Universitaet Mainz
Becherweg 21
55099 Mainz
Tel: +496131/3924662 (Maschinenraum)
Tel: +496131/3924144 (Buero)
FAX: +496131/3923532
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021102123039.X26303-100000>