The following is a message sent to the group on Wed, 26 Sep 2007 (I'm getting
this via the web since this was sent before I joined the list, and started
keeping my own copies of everything):
Kern,
I think I have found the cause of the MTEOM errors that I have been
experiencing from time to
Hello,
Thanks for the feedback -- very interesting. I'll add this to the manual so
that others will be aware of the problems that powering off a unit can cause.
Regards,
Kern
On Wednesday 26 September 2007 21:19, Mike Seda wrote:
Kern,
I think I have found the cause of the MTEOM errors
Kern,
I think I have found the cause of the MTEOM errors that I have been
experiencing from time to time. These MTEOM errors are not caused by Bacula.
In the past few months, I have rebooted my Quantum PX502 library a few
times (once every two months or so) while a tape was mounted in the
Mike Seda wrote:
Kern,
I think I have found the cause of the MTEOM errors that I have been
experiencing from time to time. These MTEOM errors are not caused by Bacula.
In the past few months, I have rebooted my Quantum PX502 library a few
times (once every two months or so) while a tape
Hi,
I haven't resolved the problem yet, I'm backuping on disk at the moment.
The problem is that it's very difficult to test because it can run 10
jobs without any problems and then suddenly fail for the next one ...
I've ran the btape test / btape fill several times without any errors,
and the
I should mention that all of my other tapes are working flawlessly with
my current setup... I just have this one tape that gives MTEOM errors...
There was nothing in the system log, but I think I know what caused the
problem... I accidentally rebooted my bacula server while bacula was
writing
I have a similar MTEOM error with one of my tapes. My drive and other
tapes are totally fine. I can even restore from this tape, but just
cannot append to it. The exact error is below:
18-Mar 02:17 uwharrie-sd: Volume MSR122L3 previously written, moving
to end of data.
18-Mar 02:35
On Saturday 31 March 2007 20:38, Mike Seda wrote:
I have a similar MTEOM error with one of my tapes. My drive and other
tapes are totally fine. I can even restore from this tape, but just
cannot append to it. The exact error is below:
18-Mar 02:17 uwharrie-sd: Volume MSR122L3 previously
In response to Julien Cigar [EMAIL PROTECTED]:
We've bought a new tape drive here, a Sony SDX-700C (AIT-3), with new
tapes. I'm running Bacula 1.38.11 under (Debian) Linux (2.6.18)
I've run the btape test / btape fill with success. The tape is
initialized correctly (variable block mode +
Bill Moran wrote:
In response to Julien Cigar [EMAIL PROTECTED]:
We've bought a new tape drive here, a Sony SDX-700C (AIT-3), with new
tapes. I'm running Bacula 1.38.11 under (Debian) Linux (2.6.18)
I've run the btape test / btape fill with success. The tape is
initialized correctly
I have a Sun v20z AMD running Bacula on Solaris 10, using a Certance Ultrium LTO 2 scsi tape device.Sometimes I receive the following error during the nightly backup, after the first machine-job is correctly finished and bacula is trying to run the second machine-job.Then, I tried to reuse the
Arno Lehmann wrote:
Hello,
Mike Reinehr wrote:
On Wednesday 13 July 2005 02:42 am, Taymour A. El Erian wrote:
HI,
I had a tape which bacula failed to write on so I did mt erase and
relabeled it with label command and started to reuse it, what happened
is that I got this error from
On Wednesday 13 July 2005 02:42 am, Taymour A. El Erian wrote:
HI,
I had a tape which bacula failed to write on so I did mt erase and
relabeled it with label command and started to reuse it, what happened
is that I got this error from bacula after it wrote several jobs on the
tape
Hello,
Mike Reinehr wrote:
On Wednesday 13 July 2005 02:42 am, Taymour A. El Erian wrote:
HI,
I had a tape which bacula failed to write on so I did mt erase and
relabeled it with label command and started to reuse it, what happened
is that I got this error from bacula after it wrote
14 matches
Mail list logo
