Running out of tape when half full???
Hi,
Hope someone can shed some light on this. Suddenly my backups have
started failing due to the tape running out of space:
*** A TAPE ERROR OCCURRED: [[writing file: No space left on device]].
FAILURE AND STRANGE DUMP SUMMARY:
server1.rwa /var lev 0 STRANGE
server1.rwa /usr/local lev 0 FAILED [out of tape]
server1.rwa /usr/local lev 0 FAILED [data write: Connection reset by peer]
server1.rwa /usr/local lev 0 FAILED [dump to tape failed]
NOTES:
taper: tape DailySet202 kb 34175264 fm 16 writing file: No space left on device
However, I'm using an 80GB (uncompressed) VXA tape:
tapetype VXA2-V23 # what kind of tape it is (see tapetypes below)
define tapetype VXA2-V23 {
comment Exabyte VXA2 tape drive and V23 tapes
length 76209 mbytes
filemark 3908 kbytes
speed 3956 kps
}
Anyone have any ideas as to what's going on?
Thanks in advance,
Matt
Illegal density on dump command
Hi guys,
I'm getting all the dump failed with the following reason:
? /sbin/dump: illegal density -- 0usf
sendbackup: error [/sbin/dump returned 1]
This is my dumptype definition:
define dumptype nocomp-root-ssh {
comp-root
comment Root partitions without compression through SSH
auth ssh
ssh_keys /var/lib/amanda/.ssh/id_rsa_amdump
compress none
}
Using Amanda 2.5.1 on RHEL4.4
Regards,
--
Fabio Corazza - Engineering
NewBay Software, Ltd.
Wilson House, Fenian Street, Dublin 2, Ireland
Phone: +353 1 634 5490 - e-mail: [EMAIL PROTECTED]
Hello list
Test to see if i got this up and running correctly
error
Since a couple of days i receive this error-report when a tape backup is
made :
These dumps were to tape DATAOND05.
*** A TAPE ERROR OCCURRED: [[writing file: 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: DATAOND06.
FAILURE AND STRANGE DUMP SUMMARY:
/data/daimail lev 1 FAILED [out of tape]
/data/home lev 2 STRANGE
Now when doing amflush I get this report:
The dumps were flushed to tape DATAOND06.
*** A TAPE ERROR OCCURRED: [[writing file: Input/output error]].
Some dumps may have been left in the holding disk.
Run amflush again to flush them to tape.
The next tape Amanda expects to use is: DATAOND07.
FAILURE AND STRANGE DUMP SUMMARY:
daeserver /data/admin_intern lev 0 FAILED [out of tape]
...
NOTES:
driver: WARNING: /var/amanda/cache: 47185920 KB requested, but only
37455780 KB available.
taper: tape DATAOND06 kb 448448 fm 1 writing file: Input/output error
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
-min_intern 0 N/A 0 --N/A N/A FAILED
-ta/daimail NO FILE TO FLUSH -
-a/dossiers NO FILE TO FLUSH -
/data/homeNO FILE TO FLUSH -
-a/intranet NO FILE TO FLUSH -
(brought to you by Amanda version 2.4.4p2)
I've been searching on the internet but seem unable to find the solution.
Is this possibly due to bad tapes? Do I need to clean my tape drive (and
how?)
Is this because the cache aint big enough?
Thx for answering or advice.
Reinhart Viane
RE: error
In addition I did an amverify DATAOND
This is the report on that:
Tapes: DATAOND06
Errors found:
DATAOND06 (daeserver._data_admin__intern.20060921.0):
amrestore: 0: skipping start of tape: date 20060922 label DATAOND06
amrestore: 1: restoring daeserver._data_admin__intern.20060921.0
gzip: stdin: unexpected end of file
amrestore: 2: reached end of information
/bin/tar: Onverwacht bestandseinde in archief
/bin/tar: Error is not recoverable: exiting now
64+0 in
64+0 out
DATAOND06 ():
amrestore: WARNING: not at start of tape, file numbers will be offset
amrestore: 0: reached end of information
** No header
0+0 in
0+0 out
DATAOND06 ():
amrestore: WARNING: not at start of tape, file numbers will be offset
amrestore: 0: reached end of information
** No header
0+0 in
0+0 out
DATAOND06 ():
amrestore: WARNING: not at start of tape, file numbers will be offset
amrestore: 0: reached end of information
** No header
0+0 in
0+0 out
DATAOND06 ():
amrestore: WARNING: not at start of tape, file numbers will be offset
amrestore: 0: reached end of information
** No header
0+0 in
0+0 out
DATAOND06 ():
amrestore: WARNING: not at start of tape, file numbers will be offset
amrestore: 0: reached end of information
** No header
0+0 in
0+0 out
amverify DATAOND
vr sep 22 10:17:28 CEST 2006
Using device /dev/nht0
Volume DATAOND06, Date 20060922
** Error detected (daeserver._data_admin__intern.20060921.0)
amrestore: 0: skipping start of tape: date 20060922 label DATAOND06
amrestore: 1: restoring daeserver._data_admin__intern.20060921.0
gzip: stdin: unexpected end of file
amrestore: 2: reached end of information
/bin/tar: Onverwacht bestandseinde in archief
/bin/tar: Error is not recoverable: exiting now
64+0 in
64+0 out
** Error detected ()
amrestore: WARNING: not at start of tape, file numbers will be offset
amrestore: 0: reached end of information
** No header
0+0 in
0+0 out
** Error detected ()
amrestore: WARNING: not at start of tape, file numbers will be offset
amrestore: 0: reached end of information
** No header
0+0 in
0+0 out
** Error detected ()
amrestore: WARNING: not at start of tape, file numbers will be offset
amrestore: 0: reached end of information
** No header
0+0 in
0+0 out
** Error detected ()
amrestore: WARNING: not at start of tape, file numbers will be offset
amrestore: 0: reached end of information
** No header
0+0 in
0+0 out
** Error detected ()
amrestore: WARNING: not at start of tape, file numbers will be offset
amrestore: 0: reached end of information
** No header
0+0 in
0+0 out
Too many errors.
Since a couple of days i receive this error-report when a tape backup is
made :
These dumps were to tape DATAOND05.
*** A TAPE ERROR OCCURRED: [[writing file: 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: DATAOND06.
FAILURE AND STRANGE DUMP SUMMARY:
/data/daimail lev 1 FAILED [out of tape]
/data/home lev 2 STRANGE
Now when doing amflush I get this report:
The dumps were flushed to tape DATAOND06.
*** A TAPE ERROR OCCURRED: [[writing file: Input/output error]].
Some dumps may have been left in the holding disk.
Run amflush again to flush them to tape.
The next tape Amanda expects to use is: DATAOND07.
FAILURE AND STRANGE DUMP SUMMARY:
daeserver /data/admin_intern lev 0 FAILED [out of tape]
...
NOTES:
driver: WARNING: /var/amanda/cache: 47185920 KB requested, but only
37455780 KB available.
taper: tape DATAOND06 kb 448448 fm 1 writing file: Input/output error
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
-min_intern 0 N/A 0 --N/A N/A FAILED
-ta/daimail NO FILE TO FLUSH -
-a/dossiers NO FILE TO FLUSH -
/data/homeNO FILE TO FLUSH -
-a/intranet NO FILE TO FLUSH -
(brought to you by Amanda version 2.4.4p2)
Re: Running out of tape when half full???
On Friday 22 September 2006 04:03, Matthew Claridge wrote:
Hi,
Hope someone can shed some light on this. Suddenly my backups have
started failing due to the tape running out of space:
*** A TAPE ERROR OCCURRED: [[writing file: No space left on device]].
FAILURE AND STRANGE DUMP SUMMARY:
server1.rwa /var lev 0 STRANGE
server1.rwa /usr/local lev 0 FAILED [out of tape]
server1.rwa /usr/local lev 0 FAILED [data write: Connection reset by
peer] server1.rwa /usr/local lev 0 FAILED [dump to tape failed]
NOTES:
taper: tape DailySet202 kb 34175264 fm 16 writing file: No space left
on device
However, I'm using an 80GB (uncompressed) VXA tape:
tapetype VXA2-V23 # what kind of tape it is (see tapetypes below)
define tapetype VXA2-V23 {
comment Exabyte VXA2 tape drive and V23 tapes
length 76209 mbytes
filemark 3908 kbytes
speed 3956 kps
}
Anyone have any ideas as to what's going on?
Thanks in advance,
Matt
Are you using an adequately sized holding disk? Without that, the data
rate to the tape might be slow enough that the drive is doing a lot of
shoe-shining, which wastes space. How big is it, and whats the setting
for 'reserved' in your amanda.conf?
--
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)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
RE: error
Reinhart Viane wrote: NOTES: driver: WARNING: /var/amanda/cache: 47185920 KB requested, but only 37455780 KB available. taper: tape DATAOND06 kb 448448 fm 1 writing file: Input/output error [...] I've been searching on the internet but seem unable to find the solution. Is this possibly due to bad tapes? Do I need to clean my tape drive (and how?) This error would normally indicate an out-of-tape condition. What size are your tapes supposed to be? (Real tapes or virtual tapes on disk?) If the same error manifests itself with different tapes, try reading the files in your holding disk: cd /var/amanda/cache cat */* /dev/null It might just be you've got an error on your holding disk. Checking the syslog is certainly a good idea as well. Alex The tapes are Sony SDX1-35c 230m which are supposed to be 35Gb/70Gb (information from internet) I executed the commands you provided but this command: cat */* /dev/null is still running. I've also made an amverify (see earlier mail) maybe that can help some more. Thanks for the help allready
Re: Running out of tape when half full???
On Fri, 22 Sep 2006 at 9:03am, Matthew Claridge wrote
Hope someone can shed some light on this. Suddenly my backups have started
failing due to the tape running out of space:
*** A TAPE ERROR OCCURRED: [[writing file: No space left on device]].
FAILURE AND STRANGE DUMP SUMMARY:
server1.rwa /var lev 0 STRANGE
server1.rwa /usr/local lev 0 FAILED [out of tape]
server1.rwa /usr/local lev 0 FAILED [data write: Connection reset by peer]
server1.rwa /usr/local lev 0 FAILED [dump to tape failed]
NOTES:
taper: tape DailySet202 kb 34175264 fm 16 writing file: No space left on
device
However, I'm using an 80GB (uncompressed) VXA tape:
tapetype VXA2-V23 # what kind of tape it is (see tapetypes below)
define tapetype VXA2-V23 {
comment Exabyte VXA2 tape drive and V23 tapes
length 76209 mbytes
filemark 3908 kbytes
speed 3956 kps
}
A few options:
1) The drive is dirty and needs to be cleaned.
2) The drive somehow got put into hardware compression mode, and you're
using software compression.
3) You're dumping over the network (no holding disk), the network
connection is too slow, and thus the tape is shoeshining (which
severely reduces its capacity).
4) Something else I'm not thinking of b/c I ain't had my coffee yet.
Look in the system log (/var/log/messages on Linux, e.g.) and you should
see some messages from the tape driver with more info on the tape error.
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University
Re: error
Reinhart Viane wrote: NOTES: driver: WARNING: /var/amanda/cache: 47185920 KB requested, but only 37455780 KB available. taper: tape DATAOND06 kb 448448 fm 1 writing file: Input/output error [...] I've been searching on the internet but seem unable to find the solution. Is this possibly due to bad tapes? Do I need to clean my tape drive (and how?) This error would normally indicate an out-of-tape condition. What size are your tapes supposed to be? (Real tapes or virtual tapes on disk?) If the same error manifests itself with different tapes, try reading the files in your holding disk: cd /var/amanda/cache cat */* /dev/null It might just be you've got an error on your holding disk. Checking the syslog is certainly a good idea as well. Alex -- Alexander Jolk / BUF Compagnie tel +33-1 42 68 18 28 / fax +33-1 42 68 18 29
Re: error
Alexander Jolk wrote: If the same error manifests itself with different tapes, try reading the files in your holding disk: cd /var/amanda/cache cat */* /dev/null It might just be you've got an error on your holding disk. Checking the syslog is certainly a good idea as well. Since you told me in private mail that you don't get an error trying to read the files directly off your holding disk, the problem seems to be with the tape drive. Try cleaning it, then do an amflush. Did you check the syslog? Alex -- Alexander Jolk / BUF Compagnie tel +33-1 42 68 18 28 / fax +33-1 42 68 18 29
Re: Running out of tape when half full???
On Fri, 22 Sep 2006 at 9:03am, Matthew Claridge wrote
Hope someone can shed some light on this.
Suddenly my backups have started failing due to the tape running out of
space:
*** A TAPE ERROR OCCURRED: [[writing file: No space left on device]].
FAILURE AND STRANGE DUMP SUMMARY:
server1.rwa /var lev 0 STRANGE
server1.rwa /usr/local lev 0 FAILED [out of tape]
server1.rwa /usr/local lev 0 FAILED ["data write: Connection reset by
peer"]
server1.rwa /usr/local lev 0 FAILED [dump to tape failed]
NOTES:
taper: tape DailySet202 kb 34175264 fm 16 writing file: No space left
on device
However, I'm using an 80GB (uncompressed) VXA tape:
tapetype VXA2-V23 # what kind of tape it is (see tapetypes below)
define tapetype VXA2-V23 {
comment "Exabyte VXA2 tape drive and V23 tapes"
length 76209 mbytes
filemark 3908 kbytes
speed 3956 kps
}
A few options:
1) The drive is dirty and needs to be cleaned.
2) The drive somehow got put into hardware compression mode, and you're
using software compression.
3) You're dumping over the network (no holding disk), the network
connection is too slow, and thus the tape is shoeshining (which
severely reduces its capacity).
4) Something else I'm not thinking of b/c I ain't had my coffee yet.
Look in the system log (/var/log/messages on Linux, e.g.) and you
should see some messages from the tape driver with more info on the
tape error.
Thanks for this. The drive doesn't report current
compression settings (duh!) so I've just switched it off, cleaned the
drive and I'll see what it does tonight.
Matt
RE: error
I can access (browse) the directory listed in my amandacache (it's named
20060921)
What if I just delete this directory and see if it works then? Maybe the
lack of cache is causing the problem.
I've inserted the cleaning disk, it runs and ejects automatically after 15
seconds.
I've run amflush again, this is what I receive:
The dumps were flushed to tape DATAOND07.
*** A TAPE ERROR OCCURRED: [[writing filemark: Input/output error]].
Some dumps may have been left in the holding disk.
Run amflush again to flush them to tape.
The next tape Amanda expects to use is: DATAOND08.
FAILURE AND STRANGE DUMP SUMMARY:
daeserver /data/admin_intern lev 0 FAILED [out of tape]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:01
Dump Time (hrs:min)0:00 0:00 0:00
Output Size (meg) 0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 0.00.00.0
Tape Used (%) 0.00.00.0
Filesystems Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
USAGE BY TAPE:
Label Time Size %Nb
DATAOND07 0:00 0.00.0 0
NOTES:
driver: WARNING: /var/amanda/cache: 47185920 KB requested, but only
37455780 KB available.
taper: tape DATAOND07 kb 0 fm 0 writing filemark: Input/output error
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
daeserver-min_intern 0 N/A 0 --N/A N/A FAILED
daeserver-ta/daimail NO FILE TO FLUSH -
daeserver-a/dossiers NO FILE TO FLUSH -
daeserver/data/homeNO FILE TO FLUSH -
daeserver-a/intranet NO FILE TO FLUSH -
(brought to you by Amanda version 2.4.4p2)
Excuse for this question: but where do I find syslog on linux?
Thx again
Since you told me in private mail that you don't get an error trying to
read the files directly off your holding disk, the problem seems to be
with the tape drive. Try cleaning it, then do an amflush. Did you
check the syslog?
Alex
Re: Running out of tape when half full???
on 22/09/2006 12:00 Gene Heskett said the following:
On Friday 22 September 2006 04:03, Matthew Claridge wrote:
Hi,
Hope someone can shed some light on this. Suddenly my backups have
started failing due to the tape running out of space:
*** A TAPE ERROR OCCURRED: [[writing file: No space left on device]].
FAILURE AND STRANGE DUMP SUMMARY:
server1.rwa /var lev 0 STRANGE
server1.rwa /usr/local lev 0 FAILED [out of tape]
server1.rwa /usr/local lev 0 FAILED ["data write: Connection reset by
peer"] server1.rwa /usr/local lev 0 FAILED [dump to tape failed]
NOTES:
taper: tape DailySet202 kb 34175264 fm 16 writing file: No space left
on device
However, I'm using an 80GB (uncompressed) VXA tape:
tapetype VXA2-V23 # what kind of tape it is (see tapetypes below)
define tapetype VXA2-V23 {
comment "Exabyte VXA2 tape drive and V23 tapes"
length 76209 mbytes
filemark 3908 kbytes
speed 3956 kps
}
Anyone have any ideas as to what's going on?
Thanks in advance,
Matt
Are you using an adequately sized holding disk? Without that, the data
rate to the tape might be slow enough that the drive is doing a lot of
shoe-shining, which wastes space. How big is it, and whats the setting
for 'reserved' in your amanda.conf?
The holding disk has 3.5GB available. Reserve is left at its default.
RE: error
In addition: the syslog (/var/log/messages)
--Executing yesterdays tape backup--
Sep 21 20:00:00 daeserver su(pam_unix)[7303]: session opened for user amanda
by (uid=0)
Sep 21 20:14:19 daeserver kernel: ide-tape: ht0: I/O error, pc = a, key =
3, asc = 52, ascq = 0
Sep 21 20:14:20 daeserver last message repeated 79 times
Sep 21 20:14:20 daeserver kernel: ide-tape: ht0: I/O error, pc = 10, key =
3, asc = 52, ascq = 0
Sep 21 20:14:20 daeserver kernel: ide-tape: Couldn't write a filemark
Sep 21 20:14:20 daeserver kernel: ide-tape: ht0: I/O error, pc = 10, key =
3, asc = 52, ascq = 0
Sep 21 20:14:20 daeserver kernel: ide-tape: ht0: I/O error, pc = 10, key =
3, asc = 52, ascq = 0
Sep 21 20:21:59 daeserver su(pam_unix)[7303]: session closed for user amanda
--Reading the settings for todays tape backup--
Sep 22 09:54:08 daeserver su(pam_unix)[9106]: session opened for user amanda
by root(uid=0)
Sep 22 09:54:24 daeserver su(pam_unix)[9131]: session opened for user root
by root(uid=33)
Sep 22 09:54:34 daeserver su(pam_unix)[9167]: session opened for user amanda
by root(uid=0)
Sep 22 09:54:34 daeserver su(pam_unix)[9167]: session closed for user amanda
Sep 22 09:54:42 daeserver su(pam_unix)[9191]: session opened for user amanda
by root(uid=0)
Sep 22 09:54:42 daeserver su(pam_unix)[9191]: session closed for user amanda
Sep 22 10:00:01 daeserver su(pam_unix)[9244]: session opened for user amanda
by (uid=0)
Sep 22 10:00:22 daeserver su(pam_unix)[9244]: session closed for user amanda
Sep 22 10:33:28 daeserver kernel: ide-tape: ht0: I/O error, pc = 8, key =
3, asc = 15, ascq = 2
Sep 22 10:33:29 daeserver last message repeated 163 times
--Executing Amflush of yesterdays backup--
Sep 22 12:15:48 daeserver su(pam_unix)[9995]: session opened for user amanda
by root(uid=0)
Sep 22 12:15:49 daeserver su(pam_unix)[9995]: session closed for user amanda
Sep 22 12:16:52 daeserver su(pam_unix)[10025]: session opened for user
amanda by root(uid=0)
Sep 22 12:16:57 daeserver su(pam_unix)[10025]: session closed for user
amanda
Sep 22 12:17:59 daeserver kernel: ide-tape: ht0: I/O error, pc = 10, key =
2, asc = 4, ascq = 1
Sep 22 12:17:59 daeserver kernel: ide-tape: ht0: I/O error, pc = 2b, key =
3, asc = 52, ascq = 0
Sep 22 12:17:59 daeserver kernel: ide-tape: ht0: position_tape failed in
discard_pipeline()
Sep 22 12:17:59 daeserver kernel: ide-tape: ht0: I/O error, pc = 10, key =
3, asc = 52, ascq = 0
Sep 22 12:17:59 daeserver kernel: ide-tape: Couldn't write a filemark
I can access (browse) the directory listed in my amandacache (it's named
20060921)
What if I just delete this directory and see if it works then? Maybe the
lack of cache is causing the problem.
I've inserted the cleaning disk, it runs and ejects automatically after 15
seconds.
I've run amflush again, this is what I receive:
The dumps were flushed to tape DATAOND07.
*** A TAPE ERROR OCCURRED: [[writing filemark: Input/output error]].
Some dumps may have been left in the holding disk.
Run amflush again to flush them to tape.
The next tape Amanda expects to use is: DATAOND08.
FAILURE AND STRANGE DUMP SUMMARY:
daeserver /data/admin_intern lev 0 FAILED [out of tape]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:01
Dump Time (hrs:min)0:00 0:00 0:00
Output Size (meg) 0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 0.00.00.0
Tape Used (%) 0.00.00.0
Filesystems Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
USAGE BY TAPE:
Label Time Size %Nb
DATAOND07 0:00 0.00.0 0
NOTES:
driver: WARNING: /var/amanda/cache: 47185920 KB requested, but only
37455780 KB available.
taper: tape DATAOND07 kb 0 fm 0 writing filemark: Input/output error
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
daeserver-min_intern 0 N/A 0 --N/A N/A FAILED
daeserver-ta/daimail NO FILE TO FLUSH -
daeserver-a/dossiers NO FILE TO FLUSH -
daeserver/data/homeNO FILE TO FLUSH -
daeserver-a/intranet NO FILE TO FLUSH -
(brought to you by Amanda version 2.4.4p2)
Re: error
Reinhart Viane wrote: In addition: the syslog (/var/log/messages) --Executing yesterdays tape backup-- Sep 21 20:00:00 daeserver su(pam_unix)[7303]: session opened for user amanda by (uid=0) Sep 21 20:14:19 daeserver kernel: ide-tape: ht0: I/O error, pc = a, key = 3, asc = 52, ascq = 0 Sep 21 20:14:20 daeserver last message repeated 79 times Sep 21 20:14:20 daeserver kernel: ide-tape: ht0: I/O error, pc = 10, key = 3, asc = 52, ascq = 0 Sep 21 20:14:20 daeserver kernel: ide-tape: Couldn't write a filemark Sep 21 20:14:20 daeserver kernel: ide-tape: ht0: I/O error, pc = 10, key = 3, asc = 52, ascq = 0 Sep 21 20:14:20 daeserver kernel: ide-tape: ht0: I/O error, pc = 10, key = 3, asc = 52, ascq = 0 Please check whether your tape drive works with standard utilities (tar, dd, mt). Something seems to be seriously hosed. Have you already hard-reset everything, by power-cycling? Alex -- Alexander Jolk / BUF Compagnie tel +33-1 42 68 18 28 / fax +33-1 42 68 18 29
RE: error
[EMAIL PROTECTED] /]# tar -tf /dev/ht0 tar: /dev/ht0: Cannot read: Invoer/uitvoer fout tar: Begin van `tape', ik stop nu tar: Error is not recoverable: exiting now --Translated:-- tar: /dev/ht0: Cannot read: Input/output error tar: Start of `tape', stopping now tar: Error is not recoverable: exiting now I will try the hard reboot 2night Please check whether your tape drive works with standard utilities (tar, dd, mt). Something seems to be seriously hosed. Have you already hard-reset everything, by power-cycling? Alex
amrecover question
I have upgraded to amanda 2.5.1. I need to restore a file and when I run amrecover I get the following AMRECOVER Version 2.5.1. Contacting server on zorn ... NAK: user root from zorn.math.purdue.edu is not allowed to execute the service amindexd: Please add amindexd amidxtaped to the line in /local/Amanda/amanda/.amandahosts I did not get this under 2.4.5p1. Is this a new check under 2.5.1? Robert _ Robert P. McGraw, Jr. Manager, Computer System EMAIL: [EMAIL PROTECTED] Purdue University ROOM: MATH-807 Department of MathematicsPHONE: (765) 494-6055 150 N. University Street FAX: (419) 821-0540 West Lafayette, IN 47907-2067 smime.p7s Description: S/MIME cryptographic signature
Re: amrecover 2.5.1
* Jean-Louis Martineau [EMAIL PROTECTED] [20060921 14:33]:
Hi,
Irix doesn't have the same return value for vsnprintf as linux have.
Could you try this patch.
OK, that did it. I can restore now without an ich...
thanks, jf
PS Are these patches applied to the snapshots on iro.umontreal.ca?
Jean-Louis
Jean-Francois Malouin wrote:
* Jean-Louis Martineau [EMAIL PROTECTED] [20060921 13:04]:
Jean-Francois,
Could you send the amrecover.timestamp.debug and
amindexd.timestamp.debug files?
here they come attached.
jf
Jean-Louis
Jean-Francois Malouin wrote:
Hello,
amanda-2.5.1 on irix-6.5.x using bsdtcp auth
amrecover don't want to play ball:
yorick 130# /opt/amanda/amanda10/sbin/amrecover
AMRECOVER Version 2.5.1. Contacting server on yorick ...
220
Setting restore date to today (2006-09-21)
200
Scanning /holddisk/conf10/stk_180...
200
200
Use the setdisk command to choose dump disk to recover
amrecover setdate 2006-09-20
200
amrecover setdisk /data/nihpd/nihpd3/backup
200
bad reply: missing date field
oc!È
amrecover ls
amrecover pwd
/data/nihpd/nihpd3/backup
mrecover listhost
200-
201-
200
amrecover listdisk
200-
201-
[ large numbers of 201- lines ]
200
amrecover add .
File . doesn't exist in directory
Now I'm nervous!
jf
diff -u -r --show-c-function --exclude-from=amanda.diff
amanda-2.5.1.new/common-src/packet.c
amanda-2.5.1.new.amindexd/common-src/packet.c
--- amanda-2.5.1.new/common-src/packet.c 2006-05-25 06:44:35.0
-0400
+++ amanda-2.5.1.new.amindexd/common-src/packet.c 2006-09-21
14:26:08.0 -0400
@@ -54,6 +54,7 @@ printf_arglist_function2(void pkt_init,
const char *, fmt)
{
va_list argp;
+int len;
assert(pkt != NULL);
assert(strcmp(pkt_type2str(type), BOGUS) != 0);
@@ -62,14 +63,16 @@ printf_arglist_function2(void pkt_init,
pkt-type = type;
pkt-packet_size = 1000;
pkt-body = alloc(pkt-packet_size);
-arglist_start(argp, fmt);
-while (vsnprintf(pkt-body, pkt-packet_size, fmt, argp) =
- (int)(pkt-packet_size - 1)) {
+while(1) {
+ arglist_start(argp, fmt);
+ len = vsnprintf(pkt-body, pkt-packet_size, fmt, argp);
+ arglist_end(argp);
+ if (len (int)(pkt-packet_size - 1))
+ break;
pkt-packet_size *= 2;
amfree(pkt-body);
pkt-body = alloc(pkt-packet_size);
}
-arglist_end(argp);
pkt-size = strlen(pkt-body);
}
@@ -79,6 +82,7 @@ printf_arglist_function2(void pkt_init,
printf_arglist_function1(void pkt_cat, pkt_t *, pkt, const char *, fmt)
{
size_t len;
+int lenX;
va_list argp;
char * pktbody;
@@ -87,19 +91,19 @@ printf_arglist_function1(void pkt_cat, p
len = strlen(pkt-body);
-arglist_start(argp, fmt);
-while (vsnprintf(pkt-body + len, pkt-packet_size - len, fmt,argp) =
- (int)(pkt-packet_size - len - 1)) {
+while(1) {
+ arglist_start(argp, fmt);
+lenX = vsnprintf(pkt-body + len, pkt-packet_size - len, fmt,argp);
+ arglist_end(argp);
+ if (lenX (int)(pkt-packet_size - len - 1))
+ break;
pkt-packet_size *= 2;
pktbody = alloc(pkt-packet_size);
strncpy(pktbody, pkt-body, len);
pktbody[len] = '\0';
amfree(pkt-body);
pkt-body = pktbody;
- arglist_end(argp);
- arglist_start(argp, fmt);
}
-arglist_end(argp);
pkt-size = strlen(pkt-body);
}
diff -u -r --show-c-function --exclude-from=amanda.diff
amanda-2.5.1.new/server-src/amindexd.c
amanda-2.5.1.new.amindexd/server-src/amindexd.c
--- amanda-2.5.1.new/server-src/amindexd.c2006-07-25 14:27:57.0
-0400
+++ amanda-2.5.1.new.amindexd/server-src/amindexd.c 2006-09-21
13:47:19.0 -0400
@@ -295,7 +295,7 @@ printf_arglist_function1(static void rep
len = vsnprintf(reply_buffer, reply_buffer_size, fmt, args);
arglist_end(args);
- if (len -1 (size_t)len reply_buffer_size)
+ if (len -1 (size_t)len reply_buffer_size-1)
break;
reply_buffer_size *= 2;
@@ -334,7 +334,7 @@ printf_arglist_function1(static void lre
len = vsnprintf(reply_buffer, reply_buffer_size, fmt, args);
arglist_end(args);
- if (len -1 (size_t)len reply_buffer_size)
+ if (len -1 (size_t)len reply_buffer_size-1)
break;
reply_buffer_size *= 2;
@@ -375,7 +375,7 @@ printf_arglist_function1(static void fas
len = vsnprintf(reply_buffer, reply_buffer_size, fmt, args);
arglist_end(args);
- if (len -1 (size_t)len reply_buffer_size)
+ if (len -1 (size_t)len reply_buffer_size-1)
break;
reply_buffer_size *= 2;
diff -u -r --show-c-function --exclude-from=amanda.diff
amanda-2.5.1.new/server-src/logfile.c
Re: amrecover question
* McGraw, Robert P. [EMAIL PROTECTED] [20060922 10:58]: I have upgraded to amanda 2.5.1. I need to restore a file and when I run amrecover I get the following AMRECOVER Version 2.5.1. Contacting server on zorn ... NAK: user root from zorn.math.purdue.edu is not allowed to execute the service amindexd: Please add amindexd amidxtaped to the line in /local/Amanda/amanda/.amandahosts I did not get this under 2.4.5p1. Is this a new check under 2.5.1? http://wiki.zmanda.com/index.php/Configuring_bsd/bsdudp/bsdtcp_authentication I suggest that you have a close look at the doc on the wiki for the new features introduced with 2.5.1 jf Robert _ Robert P. McGraw, Jr. Manager, Computer System EMAIL: [EMAIL PROTECTED] Purdue University ROOM: MATH-807 Department of MathematicsPHONE: (765) 494-6055 150 N. University Street FAX: (419) 821-0540 West Lafayette, IN 47907-2067
Re: Running out of tape when half full???
On Friday 22 September 2006 08:42, Matthew Claridge wrote:
on 22/09/2006 12:00 Gene Heskett said the following:
On Friday 22 September 2006 04:03, Matthew Claridge wrote:
Hi,
Hope someone can shed some light on this. Suddenly my backups have
started failing due to the tape running out of space:
*** A TAPE ERROR OCCURRED: [[writing file: No space left on device]].
FAILURE AND STRANGE DUMP SUMMARY:
server1.rwa /var lev 0 STRANGE
server1.rwa /usr/local lev 0 FAILED [out of tape]
server1.rwa /usr/local lev 0 FAILED [data write: Connection reset by
peer] server1.rwa /usr/local lev 0 FAILED [dump to tape failed]
NOTES:
taper: tape DailySet202 kb 34175264 fm 16 writing file: No space left
on device
However, I'm using an 80GB (uncompressed) VXA tape:
tapetype VXA2-V23 # what kind of tape it is (see tapetypes below)
define tapetype VXA2-V23 {
comment Exabyte VXA2 tape drive and V23 tapes
length 76209 mbytes
filemark 3908 kbytes
speed 3956 kps
}
Anyone have any ideas as to what's going on?
Thanks in advance,
Matt
Are you using an adequately sized holding disk? Without that, the data
rate to the tape might be slow enough that the drive is doing a lot of
shoe-shining, which wastes space. How big is it, and whats the setting
for 'reserved' in your amanda.conf?
The holding disk has 3.5GB available. Reserve is left at its default.
And how big is the dle that fails? Bear in mind the reserve is 100% at
default. Meaning its all reserved for use if the tapeing fails, and will
not be used for temporary holding. You need, for that big a tape, a
holding disk that exceeds the tapes size, and a reserve setting of perhaps
-500megabytes.
For a system like yours, with an 80GB tape, I'd pickup install a 100GB
hard drive and use that for a holding disk. They're comparable to the
cost of a couple of those tapes I'd guess, certainly less than a $100 bill
at Circuit City these days. Even the slower ones should be able to supply
the tape drive in continuous streaming mode once the write starts. I
don't know the exact exchange rate, but I'd assume thats less than 40
pounds sterling on your side of the pond.
--
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)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
RE: amrecover question
I want to thank everyone slapping my hand for not reading the manual pages
first.
After I sent the email I did go to the doc and found
the information about the new .amandahosts. I corrected my .amandahosts file
that fixed this error.
Now when I try to run amrecover I get the following
##R##-zorn-[206] ## !178
sbin/amrecover -C daily
AMRECOVER Version 2.5.1. Contacting server on zorn ...
NAK: amindexd: invalid service
I have tried to look for the error on google and in the zmanda documents but I
do not see anything.
I am running Solaris 10 which does not use inetd.conf file. Here is the info
from inetadm
SCOPENAME=VALUE
name=amandaidx
endpoint_type=stream
proto=tcp
isrpc=FALSE
wait=FALSE
exec=/local/Amanda/amanda/libexec/amindexd
user=amanda
default bind_addr=
default bind_fail_max=-1
default bind_fail_interval=-1
default max_con_rate=-1
default max_copies=-1
default con_rate_offline=-1
default failrate_cnt=40
default failrate_interval=60
default inherit_env=TRUE
default tcp_trace=FALSE
default tcp_wrappers=FALSE
Thanks
Robert
From the degug file:
amandad: (sockaddr_in *)68060 = { 0, 0, 0.0.0.0 }
security_handleinit(handle=a6c40, driver=43494 (BSD))
amandad: time 0.001: accept recv REQ pkt:
SERVICE amindexd
OPTIONS features=feff9ffeff7f;auth=bsd;
amandad: time 0.001: amindexd: invalid service
amandad: time 0.001: sending NAK pkt:
ERROR amindexd: invalid service
amandad: dgram_send_addr(addr=ffbff790, dgram=58074)
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Jean-Francois Malouin
Sent: Friday, September 22, 2006 11:05 AM
To: amanda-users@amanda.org
Subject: Re: amrecover question
* McGraw, Robert P. [EMAIL PROTECTED] [20060922 10:58]:
I have upgraded to amanda 2.5.1.
I need to restore a file and when I run amrecover I get the following
AMRECOVER Version 2.5.1. Contacting server on zorn ...
NAK: user root from zorn.math.purdue.edu is not allowed to execute the
service amindexd: Please add amindexd amidxtaped to the line in
/local/Amanda/amanda/.amandahosts
I did not get this under 2.4.5p1.
Is this a new check under 2.5.1?
http://wiki.zmanda.com/index.php/Configuring_bsd/bsdudp/bsdtcp_authenticat
ion
I suggest that you have a close look at the doc on the wiki for the
new features introduced with 2.5.1
jf
Robert
_
Robert P. McGraw, Jr.
Manager, Computer System EMAIL: [EMAIL PROTECTED]
Purdue University ROOM: MATH-807
Department of MathematicsPHONE: (765) 494-6055
150 N. University Street FAX: (419) 821-0540
West Lafayette, IN 47907-2067
smime.p7s
Description: S/MIME cryptographic signature
Re: amrecover question
McGraw, Robert P. wrote: I have upgraded to amanda 2.5.1. I need to restore a file and when I run amrecover I get the following AMRECOVER Version 2.5.1. Contacting server on zorn ... NAK: user root from zorn.math.purdue.edu is not allowed to execute the service amindexd: Please add amindexd amidxtaped to the line in /local/Amanda/amanda/.amandahosts I did not get this under 2.4.5p1. Is this a new check under 2.5.1? In Amanda 2.5.1, amrecover uses Security API. Changes to xinetd configuration and .amandahosts files are required. Please see the following wiki page for detail: http://wiki.zmanda.com/index.php/Configuring_bsd/bsdudp/bsdtcp_authentication -- Thank you! Kevin Till Amanda documentation: http://wiki.zmanda.com Amanda forums:http://forums.zmanda.com
amrecover Q?
Greetings all; After fixing everything for the proper 2.5.1 syntaxes, I thought I give amrecover a try. I'm getting this warning: [EMAIL PROTECTED] amanda-2.5.1-20060922]# amrecover Daily AMRECOVER Version 2.5.1-20060922. Contacting server on coyote.coyote.den ... 220 coyote AMANDA index server (2.5.1-20060922) ready. Setting restore date to today (2006-09-22) 200 Working date set to 2006-09-22. Warning: no log files found for tape Dailys-17 written 2147-48-36 00:00:47 Warning: no log files found for tape Dailys-16 written 2147-48-36 00:00:47 Scanning /dumps... 200 Config set to Daily. 501 Host coyote.coyote.den is not in your disklist. Trying host coyote.coyote.den ... 501 Host coyote.coyote.den is not in your disklist. Trying host coyote ... 200 Dump host set to coyote. Use the setdisk command to choose dump disk to recover While that may correspond with the switch to the use of timestamps, it doesn't make all that much sense because in that case, it should be fussing about 10 more even earlier tapes because its currently on about vtape 7 of the tapecycle. Or does it quit checking once its back far enough to do a full of everything? Just curious, I'll go quietly back to lurking. -- 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) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
2.5.1 nitpicks
Hello, I've been testing 2.5.1 for a few days now and I have 2 nitpicks: With 2.4.5 'amtoc -a' produces outputfile with names label_of_tape.toc as per the man page. This doesn't seem to be the case anymore with 2.5.1 where I just get a file called tape.toc. And in the situation where more than one tape were used (runtapes1) it simply clobbers all of them except for the last tape. I had a brief look at the diff between the 2.4.5 and 2.5.1 but couldn't find anything obvious. amstatus doesn't tell you which tapes are used and how much stuff was put on them. regards jf
Re: amanda over ssh
:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc
##
...and that's all !
Here's what's in /home/amanda/coolheads/amanda.conf:
##
org Coolheads Consulting
mailto srn vtn root
dumpuser amanda
inparallel 4
netusage 6000 Kbps
dumpcycle 25
runspercycle 0
tapecycle 100 tapes
bumpsize 200 Mb
bumpdays 1
bumpmult 4
etimeout -8000
runtapes 2
tapetype Eliant-820-112m
#tapetype Eliant-820-160m
tpchanger chg-multi # the tape-changer glue script
changerfile chg-multi.conf # the tape-changer config file
labelstr ^CH[0-9][0-9]*$ # label constraint regex: all tapes must match
holdingdisk hd1 {
comment main holding disk
directory /nobackup/AMANDASPOOL # where the holding disk is
use -2000 M
chunksize 0
}
reserve 30 # percent
logdir /home/amanda/LOG
infofile /home/amanda/INFO
indexdir /home/amanda/INDEX
tapelist /home/amanda/tapelist
define tapetype Eliant-820-112m {
comment Exabyte Eliant 820 8mm drive with 112 meter tapes
length 4194304 kbytes
filemark 48 kbytes# Assuming it's the same as for EXB-8500
}
define dumptype default {
comment global definitions
program GNUTAR
compress client fast
index yes
ssh_keys /home/amanda/.ssh/id_rsa
auth ssh
}
define dumptype dimancheSlash {
default
comment root (i.e., 'slash') filesystem for dimanche
exclude list /home/amanda/coolheads/dimancheSlash-excludes
}
define interface local {
comment a local disk
use 1000 kbps
}
define interface eth0 {
comment 100 Mbps ethernet
use 400 kbps
}
##
Nothing at all appears in /home/amanda/LOG, /home/amanda/INFO, or
/home/amanda/INDEX.
Now, when I run amdump coolheads instead of amcheck -c coolheads, here's
what turns up in /home/amanda/LOG/log.20060922.0:
##
DISK planner dimanche.coolheads.com /
START planner date 20060922
INFO planner Adding new disk dimanche.coolheads.com:/.
START driver date 20060922
WARNING driver WARNING: directory /nobackup/AMANDASPOOL/20060922170424 is not
writable
STATS driver startup time 0.062
ERROR planner Request to dimanche.coolheads.com failed: EOF on read from
dimanche.coolheads.com
FINISH planner date 20060922 time 0.151
WARNING driver WARNING: got empty schedule from planner
ERROR taper no-tape [No writable valid tape found]
WARNING taper slot 2: read label `CH0058', date `20060801'
WARNING taper label CH0058 match labelstr but it not listed in the tapelist
file.
WARNING taper slot 1: read label `CH0059', date `20060801'
WARNING taper label CH0059 match labelstr but it not listed in the tapelist
file.
WARNING taper changer problem: 1 /dev/nst0
FINISH driver date 20060922 time 16.937
##
(I don't understand why /nobackup/AMANDASPOOL/20060922170424 is not
writable; the fact is that it doesn't exist. But I'm not sure that's
relevant to my problem, here.)
If I change /home/amanda/.ssh/authorized_keys so it says:
from=dimanche.coolheads.com,no-port-forwarding,no-X11-forwarding,no-agent-forwarding,command=echo
glorp ssh-rsa
B3NzaC1yc2EBIwAAAQEAt7U07t0k+Oun36tm5ULZHMyZsTM0o9gh/c1MLOXSEvGIbdHYHktP08x2YERKQLGTlJWMuVqwZc5if/0BGiJ4SHjSjRSok4mIpa9kngF+KKD1M6EAIvT9YYLhDAm4g8whuEnc/ah74i5XnLc4PhSvV13BNPA8w2gFg71IXEqksI7r7xsWFrbjLQaxsOZmmM+ZZr/11lBjVk/sYE7nwc6G33BneFqNSPDpORvu6UCnZsK7miKm6NyMyTEOs5aW5tIy0dMqjAVZa6zE6NhQMatlTGqTEco2nLzVowW15ViDFpg4Y7lzSIWOrSVl+z4kcORkGdEKbdliUUI5UgMEYyUVyQ==
[EMAIL PROTECTED]
(i.e., so the command is echo glorp), here's what happens:
##
[EMAIL PROTECTED]:~$ ssh dimanche
glorp
Connection to dimanche closed.
[EMAIL PROTECTED]:~$
##
Now that sure looks like ssh is working, right?
-- Steve
Steven R. Newcomb, Consultant
Coolheads Consulting
Co-editor, Topic Maps International Standard (ISO/IEC 13250)
Co-editor, draft Topic Maps -- Reference Model (ISO/IEC 13250-5)
[EMAIL PROTECTED]
http://www.coolheads.com
direct: +1 540 951 9773
main: +1 540 951 9774
fax:+1 540 951 9775
208 Highview Drive
Blacksburg, Virginia 24060 USA
(Confidential to all US government personnel to whom this private
letter is not addressed and who are reading it in the absence of a
specific search warrant: You are violating the law and you are
co-conspiring to subvert the Constitution that you are sworn to
defend. You can either refuse to commit this crime, or you can expect
to suffer criminal sanctions in the future, when the current
administration of the United States of America has been replaced by
one that respects the rule of law. I do not envy you for having to
make this difficult choice, but I urge you to make
Amanda Solaris 10
Is anyone running Amanda 2.5.1 on Solaris 10 host? If so could you send me the output from inetadm -l svc:/network/amanda/udp:default inetadm -l svc:/network/amandaidx/tcp:default inetadm -l svc:/network/amidxtape/tcp:default I would like to see how you have set things up. Thanks _ Robert P. McGraw, Jr. Manager, Computer System EMAIL: [EMAIL PROTECTED] Purdue University ROOM: MATH-807 Department of MathematicsPHONE: (765) 494-6055 150 N. University Street FAX: (419) 821-0540 West Lafayette, IN 47907-2067 smime.p7s Description: S/MIME cryptographic signature
Re: amanda over ssh
Amanda Backup Client Hosts Check Host key verification failed. WARNING: dimanche.coolheads.com: selfcheck request failed: EOF on read from dimanche.coolheads.com Client check: 1 host checked in 0.137 seconds, 1 problem found does dimanche.coolheads.com (the fqdn version) in the server's .ssh/known_hosts file? If not, add it and see if it helps. -- Thank you! Kevin Till Amanda documentation: http://wiki.zmanda.com Amanda forums:http://forums.zmanda.com
Amrecover fails when using tape spanning: Unexpected EOF in archive
Hi, I am trying to restore a file which is on a backup which used tape spanning. I am running version 2.5.1. The backup says it completed successfully, but I get the errors below from amrecover and imidxtaped. Any ideas? Thanks!! David amrecover output Looking for tape 104... tar: Read 8192 bytes from - tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now Extractor child exited with status 2 debug log for amidxtaped ~~~ midxtaped: 46: restoring split dumpfile: date 20060920 host helix disk /mnt/dataa/invention part 46/UNKNOWN lev 0 comp N program /bin/tar amidxtaped: 47: restoring split dumpfile: date 20060920 host helix disk /mnt/dataa/invention part 47/UNKNOWN lev 0 comp N program /bin/tar amidxtaped: 48: restoring split dumpfile: date 20060920 host helix disk /mnt/dataa/invention part 48/UNKNOWN lev 0 comp N program /bin/tar amidxtaped: 49: restoring split dumpfile: date 20060920 host helix disk /mnt/dataa/invention part 49/UNKNOWN lev 0 comp N program /bin/tar amidxtaped: 50: restoring split dumpfile: date 20060920 host helix disk /mnt/dataa/invention part 50/UNKNOWN lev 0 comp N program /bin/tar amidxtaped: 51: restoring split dumpfile: date 20060920 host helix disk /mnt/dataa/invention part 51/UNKNOWN lev 0 comp N program /bin/tar amidxtaped: restore read error: Device or resource busy amidxtaped: time 2988.892: restore read error: Device or resource busy amidxtaped: time 2988.892: pid 18574 finish time Fri Sep 22 11:29:43 2006
Re: 2.5.1 nitpicks
Jean-Francois,
Could you try this patch?
Jean-Louis
Jean-Francois Malouin wrote:
Hello,
I've been testing 2.5.1 for a few days now and I have 2 nitpicks:
With 2.4.5 'amtoc -a' produces outputfile with names
label_of_tape.toc as per the man page. This doesn't seem to be the
case anymore with 2.5.1 where I just get a file called tape.toc. And
in the situation where more than one tape were used (runtapes1) it
simply clobbers all of them except for the last tape. I had a brief
look at the diff between the 2.4.5 and 2.5.1 but couldn't find
anything obvious.
amstatus doesn't tell you which tapes are used and how much stuff was
put on them.
regards
jf
diff -u -r --show-c-function --exclude-from=amanda.diff amanda-2.5.2alpha.new/server-src/amstatus.pl.in amanda-2.5.2alpha.new.taperstart/server-src/amstatus.pl.in
--- amanda-2.5.2alpha.new/server-src/amstatus.pl.in 2006-09-12 06:42:35.0 -0400
+++ amanda-2.5.2alpha.new.amtoc/server-src/amstatus.pl.in 2006-09-22 16:19:31.0 -0400
@@ -732,7 +732,7 @@ while(AMDUMP) {
}
}
}
- elsif(/taper: wrote label `(\S*)'/) {
+ elsif(/taper: .*wrote label `(\S*)'/) {
$nb_tape++;
$ntlabel{$nb_tape} = $1;
$ntpartition{$nb_tape} = 0;
diff -u -r --show-c-function --exclude-from=amanda.diff amanda-2.5.2alpha.new/server-src/amtoc.pl.in amanda-2.5.2alpha.new.taperstart/server-src/amtoc.pl.in
--- amanda-2.5.2alpha.new/server-src/amtoc.pl.in 2006-09-11 11:30:09.0 -0400
+++ amanda-2.5.2alpha.new.amtoc/server-src/amtoc.pl.in 2006-09-22 16:16:03.0 -0400
@@ -166,7 +166,7 @@ while ( $IF ) {
$level = $6;
switch: {
/START taper/ do {
- $tocfilename=tfn($level) if ($#subs = 0);
+ $tocfilename=tfn($chunk) if ($#subs = 0);
if (!$tocfilename || ($tocfilename eq '-')) {$OF=STDOUT;}
else {
die (Cannot open tocfile $tocfilename) unless open(OF,$tocfilename);
RE: error
Excuse my but I have the same problem with an SONY SDX-460V with 40-104 Gb tape (AIT-1 Turbo). I think since last linux update, backup stop working with the same error: These dumps were to tape DailySet101. *** A TAPE ERROR OCCURRED: [[writing file: 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: DailySet101. I tried with the cleaning tape but I got the same result. Could be the linux update who began the problem? Santiago -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Reinhart Viane Sent: Friday, September 22, 2006 11:08 AM To: 'Alexander Jolk' Cc: amanda-users@amanda.org Subject: RE: error [EMAIL PROTECTED] /]# tar -tf /dev/ht0 tar: /dev/ht0: Cannot read: Invoer/uitvoer fout tar: Begin van `tape', ik stop nu tar: Error is not recoverable: exiting now --Translated:-- tar: /dev/ht0: Cannot read: Input/output error tar: Start of `tape', stopping now tar: Error is not recoverable: exiting now I will try the hard reboot 2night Please check whether your tape drive works with standard utilities (tar, dd, mt). Something seems to be seriously hosed. Have you already hard-reset everything, by power-cycling? Alex
