> On Mon, 9 Feb 2009 13:31:20 +0100, Kern Sibbald said:
>
> On Monday 09 February 2009 13:10:12 Martin Simmons wrote:
> > > On Sat, 7 Feb 2009 12:17:33 +0100, Kern Sibbald said:
> > >
> > > On Saturday 07 February 2009 11:33:58 Ralf Gross wrote:
> > > > Kern Sibbald schrieb:
> > > > > The
On Monday 09 February 2009 13:10:12 Martin Simmons wrote:
> > On Sat, 7 Feb 2009 12:17:33 +0100, Kern Sibbald said:
> >
> > On Saturday 07 February 2009 11:33:58 Ralf Gross wrote:
> > > Kern Sibbald schrieb:
> > > > The problem described in the email below is probably an important
> > > > data
> On Sat, 7 Feb 2009 12:17:33 +0100, Kern Sibbald said:
>
> On Saturday 07 February 2009 11:33:58 Ralf Gross wrote:
> > Kern Sibbald schrieb:
> > > The problem described in the email below is probably an important data
> > > loss problem due (most likely) to an I/O error, but more importantly
On Saturday 07 February 2009 12:26:12 Ralf Gross wrote:
> Kern Sibbald schrieb:
> > On Saturday 07 February 2009 11:33:58 Ralf Gross wrote:
> > > Kern Sibbald schrieb:
> > > > The problem described in the email below is probably an important
> > > > data loss problem due (most likely) to an I/O err
Kern Sibbald schrieb:
> On Saturday 07 February 2009 11:33:58 Ralf Gross wrote:
> > Kern Sibbald schrieb:
> > > The problem described in the email below is probably an important data
> > > loss problem due (most likely) to an I/O error, but more importantly due
> > > to a misconfigured tape drive.
On Saturday 07 February 2009 11:33:58 Ralf Gross wrote:
> Kern Sibbald schrieb:
> > The problem described in the email below is probably an important data
> > loss problem due (most likely) to an I/O error, but more importantly due
> > to a misconfigured tape drive. From the information I see belo
Kern Sibbald schrieb:
>
> The problem described in the email below is probably an important data loss
> problem due (most likely) to an I/O error, but more importantly due to a
> misconfigured tape drive. From the information I see below, it appears to me
> that you have lost significant data.
On Thu, Feb 05, 2009 at 04:54:33PM +0100, Bastian Friedrich wrote:
> Hi,
>
> On Wednesday 04 February 2009, Ralf Gross wrote:
> >
> > JobId 9250: Error: block.c:568 Write error at 411:14724 on device
> > "ULTRIUM-TD4-D2" (/dev/ULTRIUM-TD4-D2). ERR=Eingabe-/Ausgabefehler.
> > JobId 9250: Error: Re
Hi,
On Wednesday 04 February 2009, Ralf Gross wrote:
>
> JobId 9250: Error: block.c:568 Write error at 411:14724 on device
> "ULTRIUM-TD4-D2" (/dev/ULTRIUM-TD4-D2). ERR=Eingabe-/Ausgabefehler.
> JobId 9250: Error: Re-read of last block OK, but block numbers differ.
> Last block=32305
Kern Sibbald schrieb:
> On Thursday 05 February 2009 12:48:18 Ralf Gross wrote:
> > Hello,
> >
> > > The problem described in the email below is probably an important data
> > > loss problem due (most likely) to an I/O error, but more importantly due
> > > to a misconfigured tape drive. From the i
On Thursday 05 February 2009 12:48:18 Ralf Gross wrote:
> Hello,
>
> > The problem described in the email below is probably an important data
> > loss problem due (most likely) to an I/O error, but more importantly due
> > to a misconfigured tape drive. From the information I see below, it
> > app
Hello,
> The problem described in the email below is probably an important data loss
> problem due (most likely) to an I/O error, but more importantly due to a
> misconfigured tape drive. From the information I see below, it appears to me
> that you have lost significant data. This is probabl
Hello,
The problem described in the email below is probably an important data loss
problem due (most likely) to an I/O error, but more importantly due to a
misconfigured tape drive. From the information I see below, it appears to me
that you have lost significant data. This is probably due to
Ralf Gross schrieb:
> Hi,
>
> I have a problem with a new lto-4 tape. Only 411 GB were written on it, then
> bacula detected an write error.
>
> JobId 9250: Error: block.c:568 Write error at 411:14724 on device
> "ULTRIUM-TD4-D2"
> (/dev/ULTRIUM-TD4-D2). ERR=Eingabe-/Ausgabefehler.
Hi,
I have a problem with a new lto-4 tape. Only 411 GB were written on it, then
bacula detected an write error.
JobId 9250: Error: block.c:568 Write error at 411:14724 on device
"ULTRIUM-TD4-D2"
(/dev/ULTRIUM-TD4-D2). ERR=Eingabe-/Ausgabefehler.
JobId 9250: Error: Re-read of last
15 matches
Mail list logo