Hi Toomas,
I really appreciate your response, my comments and answers below.
At 10:58 AM 4/19/2007, Toomas Aas wrote:
Richard Stockton wrote:
I am unable to get amanda to write to my new Quantum DLT-S4 drive.
I am trying to write directly to tape with no "holding" space.
OS: FreeBSD 6.2-RELEASE #0
Amanda: 2.5.1p3
Tapes label okay, and "amcheck" is happy, but when I do an "amdump bak15"
I get errors. Here are the log and amdump files, plus the lines that
repeat in my syslog, and the various ".debug" files and my amanda.conf
(sorry for the lengthy email, but I wanted you to have all the info).
log:
DISK planner bak-05 aacd3s1d
START planner date 20070412122332
START driver date 20070412122332
WARNING planner Last full dump of bak-05:aacd3s1d on
tape overwritten in 1 run.
STATS driver startup time 0.020
START taper datestamp 20070412122332 label VOL153 tape 0
FINISH planner date 20070412122332 time 131.949
INFO taper tape VOL153 kb 0 fm 1 writing file: Input/output error
> FAIL taper bak-05 aacd3s1d 20070412122332 0 [out of tape]
Well, gosh. Almost immediately after taping begins there is an I/O
error. This doesn't look good at all.
I agree. [sigh]
/var/log/messages:
Apr 12 12:26:54 bak-05 kernel: (sa0:ahc2:0:5:0): Unexpected busfree
in Data-out phase
Apr 12 12:26:54 bak-05 kernel: SEQADDR == 0x85
Apr 12 12:26:54 bak-05 kernel: (sa0:ahc2:0:5:0): WRITE FILEMARKS.
CDB: 10 0 0 0 1 0
Apr 12 12:26:54 bak-05 kernel: (sa0:ahc2:0:5:0): CAM Status: SCSI
Status Error
Apr 12 12:26:54 bak-05 kernel: (sa0:ahc2:0:5:0): SCSI Status: Check Condition
Apr 12 12:26:54 bak-05 kernel: (sa0:ahc2:0:5:0): Deferred Error:
ABORTED COMMAND csi:0,0,0,2 asc:44,82
Apr 12 12:26:54 bak-05 kernel: (sa0:ahc2:0:5:0): Vendor Specific ASCQ
Apr 12 12:26:54 bak-05 kernel: (sa0:ahc2:0:5:0): Retries Exhausted
Apr 12 12:26:54 bak-05 kernel: (sa0:ahc2:0:5:0): tape is now
frozen- use an OFFLINE, REWIND or MTEOM command to clear this state.
This really looks like a hardware problem, or compatibility problem
between your tape drive and FreeBSD (which would be a surprise).
Since labelling tapes is successful, the tape drive must be at least
somewhat functional.
Well, the tape labeling is not as successful as I first thought. It does
succeed eventually, but initial labeling attempts often fail with
"Input/output error".
=========================================================================
:> amlabel -f bak13 VOL134
rewinding, reading label, not an amanda tape
rewinding, writing label VOL134
amlabel: writing label: Input/output error
:> amlabel -f bak13 VOL134
rewinding, reading label, not an amanda tape
rewinding, writing label VOL134
amlabel: writing endmark: Input/output error
:> amlabel -f bak13 VOL134
rewinding, reading label, not an amanda tape (Input/output error)
rewinding, writing label VOL134, checking label, done.
:> amlabel -f bak13 VOL134
rewinding, reading label VOL134, tape is active
rewinding, writing label VOL134, checking label, done.
=======================================================================
Once it succeeds, "amcheck" appears to be happy, and "amcheck -w" succeeds,
but any write attempts by tar or dump or amanda still fail.
=======================================================================
:> amcheck bak13
Amanda Tape Server Host Check
-----------------------------
read label `VOL134', date `X'
NOTE: skipping tape-writable test
Tape VOL134 label ok
Server check took 0.035 seconds
Amanda Backup Client Hosts Check
--------------------------------
Client check: 1 host checked in 0.066 seconds, 0 problems found
(brought to you by Amanda 2.5.1p3)
:> amcheck -w bak13
Amanda Tape Server Host Check
-----------------------------
read label `VOL134', date `X'
Tape VOL134 is writable; rewrote label.
Server check took 10.905 seconds
Amanda Backup Client Hosts Check
--------------------------------
Client check: 1 host checked in 0.064 seconds, 0 problems found
(brought to you by Amanda 2.5.1p3)
========================================================================
Are you able to write any significant amount of data (more than
Amanda's 32 kB label) to tape with utilities such as dump or tar?
No. tar gives "Write error: Operation not permitted".
What is your tape blocksize set to? Amanda internally uses 32 kB
blocksize and I have seen some problems when tape blocksize is set
to something else, such as 1 kB. I've found it best to set the
blocksize to variable (mt blocksize 0).
It is set to variable;
======================================================================
> mt status
Mode Density Blocksize bpi Compression
Current: 0x4b variable 0 disabled
---------available modes---------
0: 0x4b variable 0 IDRC
1: 0x4b variable 0 IDRC
2: 0x4b variable 0 IDRC
3: 0x4b variable 0 IDRC
---------------------------------
Current Driver State: at rest.
---------------------------------
File Number: 0 Record Number: 0 Residual Count 0
======================================================================
I disabled compression using "mt comp 0", but it didn't seem to help.
I _do_ notice that there is no drive listed after the "2x4b" as there
is on my other backup boxes.
I'm at a loss here, is anyone else using the Quantum DLT-S4 with amanda?
I would appreciate any enlightenment or ideas of what to try next.
Thanks.
- Richard
|
