Bacula-users

[Bacula-users] Fatal error: Unable to write EOF

2011-11-17 04:49:04
Subject: [Bacula-users] Fatal error: Unable to write EOF
From: Ghislain Escorne <Ghislain.Escorne AT ujf-grenoble DOT fr>
To: Bacula-users AT lists.sourceforge DOT net
Date: Thu, 17 Nov 2011 10:46:39 +0100
Hello !

I have bacula  Version: 5.2.1.
I want to backup datas on a autoloader quantum i80 with 2 drives.

The bacula test works correctly:
root@backup1:~# btape -c bacula-sd.conf /dev/nst0                                                                                            .
btape: btape.c:476 open device "Drive-i80-1" (/dev/nst0): OK
*test
...
We should be in file 5. I am at file 5. This is correct!
Do you wish to continue with the Autochanger test? (y/n): y
=== Autochanger test ===
The test autochanger worked!!

But when I run a job I have this mess :

15-Nov 23:33 backup1-sd JobId 3: Writing spooled data to Volume. Despooling 107,374,192,579 bytes ...
15-Nov 23:56 backup1-sd JobId 3: Fatal error: Unable to write EOF. ERR=dev.c:1551 ioctl MTWEOF error on "Drive-i80-1" (/dev/nst0). ERR=Input/output error.

15-Nov 23:56 backup1-sd JobId 3: Fatal error: spool.c:302 Fatal append error on device "Drive-i80-1" (/dev/nst0): ERR=dev.c:1551 ioctl MTWEOF error on "Drive-i80-1" (/dev/nst0). ERR=Input/output error.

15-Nov 23:56 backup1-sd JobId 3: Despooling elapsed time = 00:21:43, Transfer rate = 82.40 M Bytes/second
15-Nov 23:56 backup1-sd JobId 3: Job write elapsed time = 06:49:12, Transfer rate = 17.47 M Bytes/second
15-Nov 23:56 backup1-fd JobId 3: Error: bsock.c:389 Write error sending 65536 bytes to Storage daemon:backup1:9103: ERR=Connection reset by peer
15-Nov 23:56 backup1-fd JobId 3: Fatal error: backup.c:1144 Network send error to SD. ERR=Connection reset by peer
15-Nov 23:56 backup1-dir JobId 3: Error: Bacula backup1-dir 5.2.1 (30Oct11):

This is my conf :
Autochanger {
  Name = i80
  Device = Drive-i80-1, Drive-i80-2
  #Changer Command = "/home/kern/bacula/bin/mtx-changer %c %o %S %a %d"
  Changer Command = "/etc/bacula/mtx-changer %c %o %S %a %d"
                    # %c = changer device
                    # %o = command (unload|load|loaded|list|slots)
                    # %S = slot index (1-based)
                    # %a = archive device (i.e., /dev/sd* name for tape drive)
                    # %d = drive index (0-based)
  Changer Device = /dev/sg3
}

Device {
  Name = Drive-i80-1
  Drive Index = 0
  ##Device Type = Tape
  Media Type = LTO5
  Archive Device = /dev/nst0
  Autochanger = yes
  LabelMedia = no;
  AutomaticMount = yes;
  AlwaysOpen = yes;
#  RemovableMedia = yes;
#  RandomAccess = no;
  Spool Directory = /data/bacula/spool
  Maximum Spool Size = 100 G  #
#  Autoselect = yes
  Maximum Changer Wait = 6000
  Alert Command = "sh -c 'tapeinfo -f %c |grep TapeAlert|cat'"
}


Device {
  Name = Drive-i80-2
  Drive Index = 1
##  Device Type = Tape
  Media Type = LTO5
  Archive Device = /dev/nst1
  Autochanger = yes
  LabelMedia = no;
  AutomaticMount = yes;
  AlwaysOpen = yes;
 # RemovableMedia = yes;
 # RandomAccess = no;
  Spool Directory = /data/bacula/spool
  Maximum Spool Size = 100 G  #
 # Autoselect = yes
  Maximum Changer Wait = 6000
  Alert Command = "sh -c 'tapeinfo -f %c |grep TapeAlert|cat'"
}

Thank you for your help

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, 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-novd2d
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
<Prev in Thread] Current Thread [Next in Thread>