rks and the later ones stop working with
---
Hostname: chronos
Org : a2g-2
Config : a2g-2
Date: May 17, 2018
*** A TAPE ERROR OCCURRED: [no drives available].
Some dumps may have been left in the holding disk.
The next 3 tapes Amanda expects to use are: a2g-2-03, a2g-2-09, a2
backup I recieve the error-message for quite a few days.
These dumps were to tape AKREG1-08.
*** A TAPE ERROR OCCURRED: [runtapes volumes already written].
There are 506710M of dumps left in the holding disk.
Run amflush to flush them to tape.
Beside this error, I found the following lines
Hi there,
during my daily backup I recieve the error-message for quite a few days.
These dumps were to tape AKREG1-08.
*** A TAPE ERROR OCCURRED: [runtapes volumes already written].
There are 506710M of dumps left in the holding disk.
Run amflush to flush them to tape.
Beside this error, I
On 03/29/2012 09:17 AM, Markus Lauterbach wrote:
Hi there,
during my daily backup I recieve the error-message for quite a few days.
These dumps were to tape AKREG1-08.
*** A TAPE ERROR OCCURRED: [runtapes volumes already written].
There are 506710M of dumps left in the holding disk.
Run amflush
Hi there,
during my daily backup I recieve the error-message for quite a few days.
These dumps were to tape AKREG1-08.
*** A TAPE ERROR OCCURRED: [runtapes volumes already written].
There are 506710M of dumps left in the holding disk.
Run amflush to flush them to tape.
Beside this error, I
Hello List,
i am trying to backup to disk and i am getting the error:
*** A TAPE ERROR OCCURRED: [new tape not found in rack].
i get the same error when i try to run amflush DailySet1.
Any ideas or tips?
Here is my amanda.conf:
org DailySet1
mario wrote:
Hello List,
i am trying to backup to disk and i am getting the error:
*** A TAPE ERROR OCCURRED: [new tape not found in rack].
i get the same error when i try to run amflush DailySet1.
Any ideas or tips?
Here is my amanda.conf
On Thursday 08 February 2007 17:38, Frank Smith wrote:
mario wrote:
Hello List,
i am trying to backup to disk and i am getting the error:
*** A TAPE ERROR OCCURRED: [new tape not found in rack].
i get the same error when i try to run amflush DailySet1.
Any ideas or tips?
Here is my
{quote}
Date: Wed, 31 Jan 2007 09:06:53 -0500 (EST)
From: Joshua Baker-LePain [EMAIL PROTECTED]
To: Adriana Liendo [EMAIL PROTECTED]
Cc: amanda-users@amanda.org
Bcc: [EMAIL PROTECTED]
Subject: Re: A TAPE ERROR OCCURRED
On Wed, 31 Jan 2007 at 8:33am, Adriana Liendo wrote
FAILURE AND STRANGE DUMP
On Sat, Feb 03, 2007 at 12:21:56PM -0400, Adriana Liendo wrote:
Hello,
Sorry, some message coming from the list were marked as spam, probably I
got your message before I release it.
Thanks for your help, but I don't understand everything. When you say I
was not using a holding
On Sat, 3 Feb 2007 at 12:21pm, Adriana Liendo wrote
In the system log there are a lot of message related to amanda, but all of
them have to do with sendmail, I guest it has to do with the message I
receive, but I don't know what else I should look at.
Look for messages regarding the tape
to change the tape once, and now it always gives me the following error:
These dumps were to tape humbolt-017.
*** A TAPE ERROR OCCURRED: [[writing file: short write]].
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: humbolt-018
I already sent a response to this message, last time you sent it:
\begin{quote}
Date: Wed, 31 Jan 2007 09:06:53 -0500 (EST)
From: Joshua Baker-LePain [EMAIL PROTECTED]
To: Adriana Liendo [EMAIL PROTECTED]
Cc: amanda-users@amanda.org
Bcc: [EMAIL PROTECTED]
Subject: Re: A TAPE ERROR OCCURRED
to change the tape once, and now it always gives me the following error:
These dumps were to tape humbolt-017.
*** A TAPE ERROR OCCURRED: [[writing file: short write]].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use
On Wed, 31 Jan 2007 at 8:33am, Adriana Liendo wrote
FAILURE AND STRANGE DUMP SUMMARY:
humbolt /sda/seis lev 0 FAILED [out of tape]
humbolt /sda/seis lev 0 FAILED [data write: Broken pipe]
humbolt /sda/seis lev 0 FAILED [dump to tape failed]
These messages indicate that the dump was
Olivier Nicole wrote:
tapetype: could not rewind /dev/nst0: Input/output error
Did you run tapetype as root?
Yes. And mt -f /dev/nst0 rewind works prefect.
Sven
:
Output Size (meg) 1.10.01.1
I'v never seen this under NOTES:
NOTES:
taper: tape daily26 kb 0 fm 0 writing filemark: Input/output error
Sven
--
I attach the whole report:
These dumps were to tape daily26.
*** A TAPE ERROR OCCURRED
NOTES:
taper: tape daily26 kb 0 fm 0 writing filemark: Input/output error
Sory for replaying to my own message. I found something in syslog:
kernel: st0: Error with sense data: Info fld=0x1, Current st
09:00: sense key Medium Error
kernel: Additional sense indicates Write error
I think
Alexandre Oliva wrote:
I think that means the tape is broken...?
Quite possibly. Try running tapetype on it and see how far it goes.
tapetype did not complain but it found 44235 mbytes on a DDS3 (without hw
compression). And I got a
tapetype: could not rewind /dev/nst0: Input/output error
tapetype did not complain but it found 44235 mbytes on a DDS3 (without hw
compression). And I got a
Tell me the trick you did with your drive to store 44 GB on a DDS-3
tape! ;-)
You should get something around 11.900 MB without and 9.500 MB with
hardware compression (yes, random data (i.e.
tapetype: could not rewind /dev/nst0: Input/output error
Did you run tapetype as root?
Olivier
I got the following error:
--
These dumps were to tape daily26.
*** A TAPE ERROR OCCURRED: [[writing file: Bad file descriptor]].
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: daily27.
[snip]
FAILED
22 matches
Mail list logo
