Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Bacula\-users\]\s+Catastrophic\s+error\.\s+Cannot\s+write\s+overflow\s+block\s+to\s+device\s+\"LTO4\"\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Bacula\-users\]\s+Catastrophic\s+error\.\s+Cannot\s+write\s+overflow\s+block\s+to\s+device\s+\"LTO4\"\s*$/: 10 ]

Total 10 documents matching your query.

1. [Bacula-users] Catastrophic error. Cannot write overflow block to device "LTO4" (score: 1): Author: "Steve Costaras" <stevecs AT chaven DOT com>; Date: Sun, 10 Jul 2011 12:17:55 +0000; 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 t; /usr/local/webapp/mharc-adsm.org/html/Bacula-users/2011-07/msg00108.html (16,704 bytes)
2. Re: [Bacula-users] Catastrophic error. Cannot write overflow block to device "LTO4" (score: 1): Author: Dan Langille <dan AT langille DOT org>; Date: Sun, 10 Jul 2011 13:58:31 -0400; I don't know. Perhaps someone else will. This I do know. Although, at first glance it seems easy to do this, it is not. If it was trivial to do, I assure you, it would already be in place. I suggest; /usr/local/webapp/mharc-adsm.org/html/Bacula-users/2011-07/msg00114.html (19,203 bytes)
3. Re: [Bacula-users] Catastrophic error. Cannot write overflow block to device "LTO4" (score: 1): Author: "James Harper" <james.harper AT bendigoit.com DOT au>; Date: Mon, 11 Jul 2011 09:42:25 +1000; This probably isn't helpful, but why does Bacula think that the volume is read-only? James -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive; /usr/local/webapp/mharc-adsm.org/html/Bacula-users/2011-07/msg00119.html (13,507 bytes)
4. Re: [Bacula-users] Catastrophic error. Cannot write overflow block to device "LTO4" (score: 1): Author: "Steve Costaras" <stevecs AT chaven DOT com>; Date: Mon, 11 Jul 2011 00:30:28 +0000; 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; /usr/local/webapp/mharc-adsm.org/html/Bacula-users/2011-07/msg00121.html (14,123 bytes)
5. Re: [Bacula-users] Catastrophic error. Cannot write overflow block to device "LTO4" (score: 1): Author: "James Harper" <james.harper AT bendigoit.com DOT au>; Date: Mon, 11 Jul 2011 10:37:40 +1000; 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"); /usr/local/webapp/mharc-adsm.org/html/Bacula-users/2011-07/msg00122.html (13,583 bytes)
6. Re: [Bacula-users] Catastrophic error. Cannot write overflow block to device "LTO4" (score: 1): Author: "Steve Costaras" <stevecs AT chaven DOT com>; Date: Mon, 11 Jul 2011 01:10:14 +0000; Nothing related to bacula/tape modules. I am running zfsonlinux for the file system here and there is a known bug with that causing soft lockups for 60-120 seconds: [121423.079640] BUG: soft lockup; /usr/local/webapp/mharc-adsm.org/html/Bacula-users/2011-07/msg00123.html (13,504 bytes)
7. Re: [Bacula-users] Catastrophic error. Cannot write overflow block to device "LTO4" (score: 1): Author: Martin Simmons <martin AT lispworks DOT com>; Date: Mon, 11 Jul 2011 12:13:53 +0100; 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 th; /usr/local/webapp/mharc-adsm.org/html/Bacula-users/2011-07/msg00130.html (14,478 bytes)
8. Re: [Bacula-users] Catastrophic error. Cannot write overflow block to device "LTO4" (score: 1): Author: Steve Costaras <stevecs AT chaven DOT com>; Date: Mon, 11 Jul 2011 16:00:15 -0500; -- *label storage=LTO4 pool=BackupSetFA volume=FA0015 Connecting to Storage daemon LTO4 at loki:9103 ... Sending label command for Volume "FA0015" Slot 14 ... 3000 OK label. VolBytes=1024 DVD=0 Volum; /usr/local/webapp/mharc-adsm.org/html/Bacula-users/2011-07/msg00148.html (27,269 bytes)
9. Re: [Bacula-users] Catastrophic error. Cannot write overflow block to device "LTO4" (score: 1): Author: Martin Simmons <martin AT lispworks DOT com>; Date: Tue, 12 Jul 2011 11:38:22 +0100; 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; /usr/local/webapp/mharc-adsm.org/html/Bacula-users/2011-07/msg00156.html (16,026 bytes)
10. Re: [Bacula-users] Catastrophic error. Cannot write overflow block to device "LTO4" (score: 1): Author: Steve Costaras <stevecs AT chaven DOT com>; Date: Tue, 12 Jul 2011 06:51:23 -0500; Yes, I pre-populate the database with the range of tapes for each pool since I already have the bar coded tapes. -- All of the data generated in your IT infrastructure is seriously valuable. Why? It; /usr/local/webapp/mharc-adsm.org/html/Bacula-users/2011-07/msg00159.html (13,287 bytes)

Current List: 1 - 10
Page: [1]