PDA

View Full Version : A TAPE ERROR OCCURRED: [No writable valid tape found] >2.5.1p2 Problem?



_demo_2
January 3rd, 2007, 01:35 AM
Hello,

I have changed from amanda 2.4.x to 2.5.1p2 on a FreeBSD 5.3 rel. system.
Amanda.conf now looks the same than in 2.4.x

So far so good. My daily backups were done correct since that day when I forgot to change the tapes.
so ...
Some dumps have been left in the holding disk ....

Now I try to amflush them to a tape as I did 100 times before (with ver. 2.4) and the following error occurs

*** A TAPE ERROR OCCURRED: [No writable valid tape found].
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: BUeC01_002.
:(


I deleted the files on the Holding disk but the error remains (amdump is showing the same error)! :confused:

a part of my amanda.conf for daily full backups
inparallel 4 # maximum dumpers that will run in parallel (max 63)
dumporder "sssS" # specify the priority order of each dumper
netusage 9000 Kbps # maximum net bandwidth for Amanda, in KB per sec
dumpcycle 1 days
runspercycle 1 # the number of amdump runs in dumpcycle days
tapecycle 4 tapes # the number of tapes in rotation
bumpsize 20 Mb # minimum savings (threshold) to bump level 1 -> 2
bumpdays 1 # minimum days at each level
bumpmult 4 # threshold = bumpsize * bumpmult^(level-1)
etimeout 2000 # number of seconds per filesystem for estimates.
dtimeout 1800 # number of idle seconds before a dump is aborted.
ctimeout 30 # maximum number of seconds that amcheck waits
tapebufs 20
runtapes 1 # number of tapes to be used in a single run of amdump
tpchanger "chg-zd-mtx" # the tape-changer glue script
tapedev "/dev/nsa0" # the no-rewind tape device to be used
rawtapedev "/dev/pass2" # the raw device to be used (ftape only)
changerfile "/usr/local/etc/amanda/config1/chg-zd-mtx.conf"
changerdev "/dev/pass3"
maxdumpsize -1 # Maximum number of bytes the planner will schedule
tapetype SDLT320 # what kind of tape it is (see tapetypes below)

_demo_2
January 3rd, 2007, 05:54 AM
ok, here is what I did to avoid the problem for this time

$amtape 01 show
amtape: scanning all 10 slots in tape-changer rack:
slot 2: date 20061216 label C01_002
slot 3: date 20061217 label C01_003
slot 4: date 20061218 label C01_004
slot 5: date 20061219 label C01_005
slot 6: date 20061220 label C01_006
slot 7: date 20060413 label C01_008
slot 1: date 20061228 label C01_001
slot 2: date 20061216 label C01_002
slot 3: date 20061217 label C01_003
slot 4: date 20061218 label C01_004

$ more tapelist
20061228 C01_001 reuse
20061227 C01_015 reuse
20061226 C01_014 reuse
20061225 C01_013 reuse
20061224 C01_012 reuse
20061223 C01_011 reuse
20061222 C01_010 reuse
20061221 C01_009 reuse
20061220 C01_006 reuse
20061219 C01_005 reuse
20061218 C01_004 reuse
20061217 C01_003 reuse
20061216 C01_002 reuse
20060413 C01_008 no-reuse
20060412 C01_007 no-reuse

$ amflush -fs 01
Scanning /hold...
20070103060001: found Amanda directory.

Today is: 20070103
Flushing dumps in 20070103060001 using tape changer "chg-zd-mtx".
Expecting tape C01_002 or a new tape. (The last dumps were to tape C01_001)
Are you sure you want to do this [yN]? y
amflush: start at Wed Jan 3 14:52:50 CET 2007
amflush: datestamp 20070103145245
FLUSH
....
....
ENDFLUSH
driver: pid 1455 executable driver version 2.5.1p2
driver: tape size 158467072
driver: adding holding disk 0 dir /hold size 48128000 chunksize 1048576
reserving 48128000 out of 48128000 for degraded-mode dumps
driver: send-cmd time 0.034 to taper: START-TAPER 20070103145245
driver: start time 0.038 inparallel 4 bandwidth 17592 diskspace 48128000 dir OBSOLETE datestamp 20070103145245 driver: drain-ends tapeq FIRST big-dumpers sssS
taper: pid 1456 executable taper version 2.5.1p2
taper: page size = 4096
taper: buffer size is 32768
changer: opening pipe to: .../chg-zd-mtx -info
changer: opening pipe to: .../chg-zd-mtx -slot current
changer: opening pipe to: .../chg-zd-mtx -slot next
changer: opening pipe to: .../chg-zd-mtx -slot next
changer: opening pipe to: .../chg-zd-mtx -slot next
changer: opening pipe to: .../chg-zd-mtx -slot next
changer: opening pipe to: .../chg-zd-mtx -slot next
driver: result time 310.162 from taper: TAPE-ERROR <nohandle> "[writing label: short write]"
driver: state time 310.162 free kps: 17592 space: 48128000 taper: idle idle-dumpers: 4 qlen tapeq: 21 runq: 0 roomq: 0 wakeup: 0 driver-idle: not-idle
driver: interface-state time 310.162 if default: free 8000 if LOCAL: free 1000 if LE0: free 400 if EM0: free 8192
driver: hdisk-state time 310.162 hdisk 0: free 48128000 dumpers 0
driver: state time 310.162 free kps: 17592 space: 48128000 taper: idle idle-dumpers: 4 qlen tapeq: 21 runq: 0 roomq: 0 wakeup: 0 driver-idle: not-idle
driver: interface-state time 310.162 if default: free 8000 if LOCAL: free 1000 if LE0: free 400 if EM0: free 8192
driver: hdisk-state time 310.162 hdisk 0: free 48128000 dumpers 0
driver: QUITTING time 310.162 telling children to quit
driver: send-cmd time 310.162 to taper: QUIT
taper: DONE [idle wait: 0.000 secs]
driver: FINISHED time 311.170
No $home variable set.
"~/.mailrc": No match.

amanda did nothing :-( so my idea was to disable this tape (which however was readable and tue to the tapelist reusable!??)

$ amadmin 01 no-reuse C01_002

now amflush is working on C01_003 :-) But I don't now what the real problem was. Maybe a broken tape...

_demo_2
January 3rd, 2007, 07:01 AM
Ok, the problem lies between the ears.
A jester activated the write protection on this one tape in the loader.

However amanda could also be more fault-tolerant