Hello, I have a similar problem to:

http://www.mail-archive.com/bacula-users AT lists.sourceforge DOT 
net/msg26187.html

but in my situation the MTEOM error seems not caused by a reboot of the 
autoloader.

My system is:

- Debian 5.0

- Bacula 2.5.42-b2

- Autoloader: Dell TL2000 (24 slot, 1 drive)

Device status:
Autochanger "TL2000" with devices:
   "ULT3580-HH4" (/dev/st0)
Device "ULT3580-HH4" (/dev/st0) is mounted with:
    Volume:      000003LU
    Pool:        Default
    Media type:  LTO4
    Slot 3 is loaded in drive 0.
    Total Bytes=584,228,477,952 Blocks=9,056,120 Bytes/block=64,512
    Positioned at File=655 Block=0
====

Used Volume status:
000003LU on device "ULT3580-HH4" (/dev/st0)
    Reader=0 writers=0 devres=0 volinuse=0


# lsscsi
[0:0:0:0]    tape    IBM      ULT3580-HH4      89B1  /dev/st0
[0:0:0:1]    mediumx IBM      3573-TL          7.40  /dev/sch0

Bacula-sd.conf:

Autochanger {
  Name = TL2000
  Device = ULT3580-HH4
  Changer Command = "/etc/bacula/mtx-changer %c %o %S %a %d"
  Changer Device = /dev/sg1
}

Device {
  Name = ULT3580-HH4
  Device Type = Tape
  Drive Index = 0
  Media Type = LTO4
  Archive Device = /dev/st0
  AutomaticMount = yes;               # when device opened, read it
  AlwaysOpen = yes;
  RemovableMedia = yes;
  RandomAccess = no;
  AutoChanger = yes;
  LabelMedia = yes;
  Maximum Changer Wait = 3d
  Alert Command = "sh -c 'tapeinfo -f %c |grep TapeAlert|cat'"
}

The error:

07-Apr 19:00 turbo-dir JobId 125: Start Backup JobId 125, 
Job=zeus-Weekly.2009-04-07_19.00.00.31
07-Apr 19:00 turbo-dir JobId 125: Using Device "ULT3580-HH4"
07-Apr 19:00 turbo-sd JobId 125: Volume "000002LU" previously written, 
moving to end of data.
07-Apr 19:12 turbo-sd JobId 125: Error: Unable to position to end of data on 
device "ULT3580-HH4" (/dev/st0): ERR=dev.c:937 ioctl MTEOM error on 
"ULT3580-HH4" (/dev/st0). ERR=Input/output error.

07-Apr 19:12 turbo-sd JobId 125: Marking Volume "000002LU" in Error in 
Catalog.
07-Apr 19:12 turbo-sd JobId 125: 3307 Issuing autochanger "unload slot 2, 
drive 0" command.
07-Apr 19:14 turbo-sd JobId 125: 3301 Issuing autochanger "loaded? drive 0" 
command.
07-Apr 19:14 turbo-sd JobId 125: 3302 Autochanger "loaded? drive 0", result: 
nothing loaded.
07-Apr 19:14 turbo-sd JobId 125: 3304 Issuing autochanger "load slot 3, 
drive 0" command.
07-Apr 19:15 turbo-sd JobId 125: 3305 Autochanger "load slot 3, drive 0", 
status is OK.
07-Apr 19:15 turbo-sd JobId 125: Volume "000003LU" previously written, 
moving to end of data.
07-Apr 19:17 turbo-sd JobId 125: Ready to append to end of Volume "000003LU" 
at file=645.

The backup works nice until I made some "move" on the tapes in the 
autoloader. For example in this case what I've done:

- in bconsole unmounted the drive (command "unmount");
- opened the right magazine and put in 5 additional tapes;
- reloaded the tape 000002LU (that was in the second slot) in the drive with 
"mtx -f /dev/sg1 load 2"

and started the jobs.

I can't understand what is writing the MTEOM marker on the tape. It's the 
second time that this happens. I'm not a tape expert under Linux and i use 
Bacula since 1 month so may be I've made some mistake in the command or 
procedure I use, is right to unmount the drive in Bacula before work with 
the autoloader? Is right to use mtx to move tapes in the autoloader and to 
mount the tape or I have to use bconsole?

What's the correct procedure now to remove my two MTEOM'ed  tapes from my 
Pool and format them to be reused in their full lenght?

Thanks for your support. 


------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users