No, I never did try that. I may if I get time. Things are busy right now, so
now that it's working again, I'm good. :)
j- k-
On Thursday 06 October 2005 13:14, Alan Brown wrote:
> On Wed, 5 Oct 2005, Joshua Kugler wrote:
> > And yet more info (long, with lots of job reports).
> >
> > T
On Wed, 5 Oct 2005, Joshua Kugler wrote:
And yet more info (long, with lots of job reports).
This error actually happened with *two* different tapes, and in both cases,
when they errored, they had the same "last volume bytes" value.
Have you tried running btape to see what it says?
---
On Wednesday 05 October 2005 23:18, Kern Sibbald wrote:
> This is somewhat of a wild shot, but I recently saw a kernel bug fix
> against the aic7xxx drivers. If I remember right (I'm a bit hazy on this)
> there was a problem after writing 35GB of data.
According to lspcidrake (Mandrake's lspci ex
Josh,
On 06.10.2005 00:38, Joshua Kugler wrote:
OK, a little more info on this weird occurrence.
what you describe looks like a driver or hardware problem to me. Alhough
I can't be sure, I'm not able to imagine anything bacula-related leading
to such problems.
If you can reproduce the pro
This is somewhat of a wild shot, but I recently saw a kernel bug fix against
the aic7xxx drivers. If I remember right (I'm a bit hazy on this) there was
a problem after writing 35GB of data.
On Thursday 06 October 2005 02:12, Joshua Kugler wrote:
> And yet more info (long, with lots of job repo
And yet more info (long, with lots of job reports).
This error actually happened with *two* different tapes, and in both cases,
when they errored, they had the same "last volume bytes" value.
This seems to be tied to network errors somehow. Observer:
The job before this one loaded tape 0009.
OK, a little more info on this weird occurrence.
I unmounted the tape in the drive (0010), and mounted the next one (0011). I
then initiated a job, and Bacula unloaded 0011 and loaded 0010 again. But it
forwarded to the end of the data, and wrote it all just fine.
Do I have a weird one-time g
I sent this yesterday and got no replies. I'll try to include more detail
this time.
Server version (SD and Dir): 1.36.1
Client version(s): 1.36.0 (on all: Linux, Mac, Windows)
This error is being generated from Windows, Mac, and Linux clients
This error suddenly popped up, with no changes to a
