>>>>> On Mon, 11 Jul 2011 16:00:15 -0500, Steve Costaras said:
> Authentication-Results: cm-omr4 smtp.user=stevecs AT chaven DOT com;
> auth=pass (CRAM-MD5)
>
> On 2011-07-11 06:13, Martin Simmons wrote:
> >>>>>> On Sun, 10 Jul 2011 12:17:55 +0000, Steve Costaras said:
> >> Importance: Normal
> >> Sensitivity: Normal
> >>
> >> I am trying a full backup/multi-job to a single client and all was going
> >> well until this morning when I received the error below. All other jobs
> >> were also canceled.
> >>
> >> My question is two fold:
> >>
> >> 1) What the heck is this error? I can unmount the drive, issue a rawfill
> >> to
> >> the tape w/ btape and no problems?
> >> ...
> >> 3000 OK label. VolBytes=1024 DVD=0 Volume="FA0016" Device="LTO4"
> >> (/dev/nst0)
> >> Requesting to mount LTO4 ...
> >> 3905 Bizarre wait state 7
> >> Do not forget to mount the drive!!!
> >> 2011-07-10 03SD-loki JobId 6: Wrote label to prelabeled Volume "FA0016" on
> >> device "LTO4" (/dev/nst0)
> >> 2011-07-10 03SD-loki JobId 6: New volume "FA0016" mounted on device "LTO4"
> >> (/dev/nst0) at 10-Jul-2011 03:51.
> >> 2011-07-10 03SD-loki JobId 6: Fatal error: block.c:439 Attempt to write on
> >> read-only Volume. dev="LTO4" (/dev/nst0)
> >> 2011-07-10 03SD-loki JobId 6: End of medium on Volume "FA0016" Bytes=1,024
> >> Blocks=0 at 10-Jul-2011 03:51.
> >> 2011-07-10 03SD-loki JobId 6: Fatal error: Job 6 canceled.
> >> 2011-07-10 03SD-loki JobId 6: Fatal error: device.c:192 Catastrophic
> >> error. Cannot write overflow block to device "LTO4" (/dev/nst0).
> >> ERR=Input/output error
> > Do you regularly see the "3905 Bizarre wait state 7" message? It could be
> > an
> > indication of problems (and everything after that could be a consequence of
> > it).
> >
> > What are the messages that lead up to that point?
> Nothing, really, this was the 17th tape in a row on a ~3day (so far)
> backup. No messages in /var/log/messages. Previous messages from
> bacula are below as you can see it just blows chunks right after FA0016
> is mounted, all concurrent jobs are killed. And I've tested that tape
> before the backup ran and again right after this failure with btape.
> no problems.
Yes, that looks mostly normal.
I would report that log output as a bug at bugs.bacula.org.
I'm a little surprised that it specifically asked for the volume named FA0016
though:
2011-07-10 03SD-loki JobId 6: Please mount Volume "FA0016" or label a new one
for:
but you then issued the label command for that volume.
Was FA0016 in the database already? If not, how did bacula predict the name?
__Martin
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
