I should mention that all of my other tapes are working flawlessly with 
my current setup... I just have this one tape that gives MTEOM errors... 
There was nothing in the system log, but I think I know what caused the 
problem... I accidentally rebooted my bacula server while bacula was 
writing to tape... The reboot operation just hung, and I hard-powered 
the bacula server off since I figured I was screwed anyway... The tape 
clearly didn't like this... I think the tape is slightly damaged... I 
can restore from it, but cannot append to it... How can I move the data 
from this tape onto another? Probably migration, huh?


Kern Sibbald wrote:
> On Saturday 31 March 2007 20:38, Mike Seda wrote:
>   
>> I have a similar MTEOM error with one of my tapes. My drive and other 
>> tapes are totally fine. I can even restore from this tape, but just 
>> cannot append to it. The exact error is below:
>>
>> 18-Mar 02:17 uwharrie-sd: Volume "MSR122L3" previously written, moving 
>> to end of data.
>> 18-Mar 02:35 uwharrie-sd: tsali.2007-03-17_23.05.00 Error: Unable to 
>> position to end of data on device "Drive-1" (/dev/nst0): ERR=dev.c:922 
>> ioctl MTEOM error on "Drive-1" (/dev/nst0). ERR=Input/output error.
>> 18-Mar 02:35 uwharrie-sd: Marking Volume "MSR122L3" in Error in Catalog.
>>
>> My setup is:
>> Bacula 2.0.1
>> RHEL 4 AS
>> Quantum PX502 (FC, 1 HP LTO-3 Drive)
>>
>> Any thoughts?
>>     
>
> Anyone who gets MTEOM errors on a tape that has been written with no error 
> messages, has a serious problem -- either improperly configured (tape drive 
> parameters/modes don't agree with those in Bacula's device resource), or 
> hardware problems.
>
> Start by looking at your system log and Bacula output for errors.  If there 
> are, then they need to be resolved.  If not, then it could well be 
> configuration so re-run the 9 (or 10) testing steps documented in the tape 
> testing chapter of the manual.
>
>   
>> Julien Cigar wrote:
>>     
>>> Bill Moran wrote:
>>>   
>>>       
>>>> In response to Julien Cigar <[EMAIL PROTECTED]>:
>>>>   
>>>>     
>>>>         
>>>>> We've bought a new tape drive here, a Sony SDX-700C (AIT-3), with new 
>>>>> tapes. I'm running Bacula 1.38.11 under (Debian) Linux (2.6.18)
>>>>> I've run the btape test / btape fill with success. The tape is 
>>>>> initialized correctly (variable block mode + ...) :
>>>>>
>>>>> phoenix:/home/jcigar# cat /etc/stinit.def
>>>>> {buffer-writes read-ahead async-writes}
>>>>>
>>>>> manufacturer=SONY model = "SDX-700C" {
>>>>> mode1 blocksize=0 compression=1
>>>>> }
>>>>>
>>>>> phoenix:/home/jcigar# mt -f /dev/nst0 status
>>>>> SCSI 2 tape drive:
>>>>> File number=0, block number=0, partition=0.
>>>>> Tape block size 0 bytes. Density code 0x32 (AIT-3).
>>>>> Soft error count since last status=0
>>>>> General status bits on (41010000):
>>>>>  BOT ONLINE IM_REP_EN
>>>>>
>>>>> Unfortunately I got an error this morning :
>>>>>
>>>>> 01-Feb 03:27 phoenix-sd: Volume "Full-Tape-0001" previously written, 
>>>>> moving to end of data.
>>>>> 01-Feb 03:27 phoenix-sd: canis-job.2007-02-01_03.00.00 Error: Unable to 
>>>>> position to end of data on device "sony SDX-700C" (/dev/nst0): 
>>>>> ERR=dev.c:839 ioctl MTEOM error on "sony SDX-700C" (/dev/nst0). 
>>>>> ERR=Input/output error.
>>>>>
>>>>> 01-Feb 03:27 phoenix-sd: Marking Volume "Full-Tape-0001" in Error in 
>>>>> Catalog.
>>>>>     
>>>>>       
>>>>>           
>>>> I'm a little unclear on certain aspects of this ...
>>>>
>>>> Have you made other backups successfully?  Did you try a different tape?
>>>> Sometimes tapes ship from the factory with problems.  Is this the same
>>>> tape that you used for the tests?
>>>>
>>>>   
>>>>     
>>>>         
>>> Yes, it runs fine since one month, and it's the same tape I've used for 
>>> the tests (after the test I made an mt -f /dev/nst0 rewind ; mt -f 
>>> /dev/nst0 weof ; mt -f /dev/nst0 rewind ; $> bconsole ; *label).
>>>
>>> I will try with another tape to see ...
>>>
>>>   
>>>       
>>>> We had a drive go bad on us and the errors that Bacula was spewing out
>>>> were the most cryptic things you could imagine.  It became obvious when
>>>> we visited the datacenter, as the drive had a flashing error code on
>>>> the front.
>>>>
>>>>   
>>>>     
>>>>         
>>>   
>>>       
>> -------------------------------------------------------------------------
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to share your
>> opinions on IT & business topics through brief surveys-and earn cash
>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>> _______________________________________________
>> Bacula-users mailing list
>> Bacula-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bacula-users
>>
>>     


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to