Re: [Bacula-users] Catastrophic error. Cannot write overflow block to device

2012-11-28 Thread lst_hoe02
Zitat von Luca Bertoncello : > Am Wed, 28 Nov 2012 15:11:29 +0100 > schrieb lst_ho...@kwsoft.de: > >> could you explain what kind of device this is and how it is >> configured in bacula? > > I use 6 hard-disk with vchanger to simulate a tape-library. > What do you need from the bacula configurati

Re: [Bacula-users] Catastrophic error. Cannot write overflow block to device

2012-11-28 Thread Luca Bertoncello
Am Wed, 28 Nov 2012 15:11:29 +0100 schrieb lst_ho...@kwsoft.de: > could you explain what kind of device this is and how it is > configured in bacula? I use 6 hard-disk with vchanger to simulate a tape-library. What do you need from the bacula configuration? Regards -- Luca Bertoncello Programmi

Re: [Bacula-users] Catastrophic error. Cannot write overflow block to device

2012-11-28 Thread lst_hoe02
Zitat von Luca Bertoncello : > Hello, list! > > Since 3 days I cannot backup my server... > I always get this error: > > 28-Nov 00:40 skynet-sd JobId 36: Fatal error: device.c:192 Catastrophic > error. Cannot write overflow block to device > "sata-changer-drive-0" (/var/lib/bacula/changer1/0/driv

Re: [Bacula-users] Catastrophic error. Cannot write overflow block to device

2012-11-28 Thread Heiko Schellhorn
Hi > schrieb Jérôme Blion : > >> ERR=No space left on device >> >> You have to make some space... > > With about 500GB free? I don't believe it is the problem... Just a guess resp. a shot to nothing Do you perhaps have a very large number of very small files on that disk ? Maybe you still ha

Re: [Bacula-users] Catastrophic error. Cannot write overflow block to device

2012-11-28 Thread Radosław Korzeniewski
Hello, 2012/11/28 Luca Bertoncello > Am Wed, 28 Nov 2012 10:20:08 +0100 > schrieb Jérôme Blion : > > > ERR=No space left on device > > > > You have to make some space... > > With about 500GB free? I don't believe it is the problem... > > Yes it is a problem. The error message is: "No space left

Re: [Bacula-users] Catastrophic error. Cannot write overflow block to device

2012-11-28 Thread Luca Bertoncello
Am Wed, 28 Nov 2012 10:20:08 +0100 schrieb Jérôme Blion : > ERR=No space left on device > > You have to make some space... With about 500GB free? I don't believe it is the problem... Regards -- Luca Bertoncello Programmierer FrischerGehts.net GmbH & Co.

Re: [Bacula-users] Catastrophic error. Cannot write overflow block to device

2012-11-28 Thread Jérôme Blion
Hello, ERR=No space left on device You have to make some space... HTH. Jerome Blion Le 2012-11-28 08:16, Luca Bertoncello a écrit : > Hello, list! > > Since 3 days I cannot backup my server... > I always get this error: > > 28-Nov 00:40 skynet-sd JobId 36: Fatal error: device.c:192 > Catastro

[Bacula-users] Catastrophic error. Cannot write overflow block to device

2012-11-27 Thread Luca Bertoncello
Hello, list! Since 3 days I cannot backup my server... I always get this error: 28-Nov 00:40 skynet-sd JobId 36: Fatal error: device.c:192 Catastrophic error. Cannot write overflow block to device "sata-changer-drive-0" (/var/lib/bacula/changer1/0/drive0). ERR=No space left on device28-Nov 00:40

Re: [Bacula-users] Catastrophic error. Cannot write overflow block to device "LTO4"

2011-07-12 Thread Steve Costaras
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"

Re: [Bacula-users] Catastrophic error. Cannot write overflow block to device "LTO4"

2011-07-12 Thread Martin Simmons
> 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

Re: [Bacula-users] Catastrophic error. Cannot write overflow block to device "LTO4"

2011-07-11 Thread Steve Costaras
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

Re: [Bacula-users] Catastrophic error. Cannot write overflow block to device "LTO4"

2011-07-11 Thread Martin Simmons
> 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

Re: [Bacula-users] Catastrophic error. Cannot write overflow block to device"LTO4"

2011-07-10 Thread Dan Langille
.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

Re: [Bacula-users] Catastrophic error. Cannot write overflow block to device"LTO4"

2011-07-10 Thread Dan Langille
On Jul 10, 2011, at 3:18 PM, Steve Costaras wrote: > > -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] Catas

Re: [Bacula-users] Catastrophic error. Cannot write overflow block to device "LTO4"

2011-07-10 Thread Steve Costaras
> 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()

Re: [Bacula-users] Catastrophic error. Cannot write overflow block to device "LTO4"

2011-07-10 Thread James Harper
> > 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:

Re: [Bacula-users] Catastrophic error. Cannot write overflow block to device "LTO4"

2011-07-10 Thread Steve Costaras
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

Re: [Bacula-users] Catastrophic error. Cannot write overflow block to device "LTO4"

2011-07-10 Thread James Harper
> > 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

Re: [Bacula-users] Catastrophic error. Cannot write overflow block to device"LTO4"

2011-07-10 Thread Steve Costaras
-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" >> >>

Re: [Bacula-users] Catastrophic error. Cannot write overflow block to device "LTO4"

2011-07-10 Thread Dan Langille
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

[Bacula-users] Catastrophic error. Cannot write overflow block to device "LTO4"

2011-07-10 Thread Steve Costaras
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