On 2011-07-12 05:38, Martin Simmons wrote:
> 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"
> On Mon, 11 Jul 2011 16:00:15 -0500, Steve Costaras said:
> Authentication-Results: cm-omr4 smtp.user=stev...@chaven.com; auth=pass
> (CRAM-MD5)
>
> On 2011-07-11 06:13, Martin Simmons wrote:
> >> On Sun, 10 Jul 2011 12:17:55 +, Steve Costaras said:
> >> Importance: Normal
> >> Sens
On 2011-07-11 06:13, Martin Simmons wrote:
>> On Sun, 10 Jul 2011 12:17:55 +, 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
> On Sun, 10 Jul 2011 12:17:55 +, 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 quest
.net
> Subject: Re: [Bacula-users] Catastrophic error. Cannot write overflow block
> to device "LTO4"
>
> >>
> >> 2) since everything is spooled first, there should be NO error that should
> >> cancel a job. A tape drive could fail, a tape could burst in
trophic error. Cannot write overflow block
> to device "LTO4"
>
> >>
> >> 2) since everything is spooled first, there should be NO error that should
> >> cancel a job. A tape drive could fail, a tape could burst into flame, all
> >> that would
> Just had a quick look... the "read-only" message is this in stored/block.c:
>
> if (!dev->can_append()) {
> dev->dev_errno = EIO;
> Jmsg1(jcr, M_FATAL, 0, _("Attempt to write on read-only Volume. dev=%s\n"),
> dev->print_name());
> return false;
> }
>
>And can_append() is:
>
>int can_append()
>
> no idea, if we can find out what triggered the original message. Without
> doing anything physical, I did an umount storage=LTO4 from bacula and then
> went and did a full btape rawfill without a single problem on the volume:
>
> *status
> Bacula status: file=0 block=1
> Device status:
11 06:42 PM
To: stev...@chaven.com, bacula-users@lists.sourceforge.net
Subject: RE: [Bacula-users] Catastrophic error. Cannot write overflow block to
device "LTO4"
>
> 3000 OK label. VolBytes=1024 DVD=0 Volume="FA0016" Device="LTO4" (/dev/nst0)
> Requesting to
>
> 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-1
-Original Message-
From: Dan Langille [mailto:d...@langille.org]
Sent: Sunday, July 10, 2011 12:58 PM
To: stev...@chaven.com
Cc: bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] Catastrophic error. Cannot write overflow block to
device "LTO4"
>>
>>
On Jul 10, 2011, at 8:17 AM, Steve Costaras wrote:
>
>
> 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 err
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 an
13 matches
Mail list logo
