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 l
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
.toc as per the man page. This doesn't seem to be the
case anymore with 2.5.1 where I
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
Looki
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 fq
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
a"
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 dis
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
.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
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
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 a
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 aman
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 o
* 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.p
* 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
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
[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: exiti
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
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
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
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 ag
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 S
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
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
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 /va
>>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 t
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:
>
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
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
Test to see if i got this up and running correctly
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"
a
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 FAI
30 matches
Mail list logo
