Bacula-users

[Bacula-users] MTFSF error positioning tape following reboot

2010-06-02 19:13:43
Subject: [Bacula-users] MTFSF error positioning tape following reboot
From: AndyW <bacula-forum AT backupcentral DOT com>
To: bacula-users AT lists.sourceforge DOT net
Date: Wed, 02 Jun 2010 19:11:29 -0400
I invariably get errors of the following kind when I try to append to a 
previously written tape following a reboot:-
31-May 23&#58;48 bacula-dir JobId 234&#58; Start Backup JobId 234, 
Job=BackupHomeDir.2010-05-31_23.48.54_04
31-May 23&#58;48 bacula-dir JobId 234&#58; Using Device "SLR7"
31-May 23&#58;49 bacula-sd JobId 234&#58; Volume "Week3-Tape001" previously 
written, moving to end of data.
31-May 23&#58;52 bacula-sd JobId 234&#58; Error&#58; Unable to position to end 
of data on device "SLR7" &#40;/dev/nst0&#41;&#58; ERR=dev.c&#58;1
396 ioctl MTFSF error on "SLR7" &#40;/dev/nst0&#41;. ERR=Input/output error.

31-May 23&#58;52 bacula-sd JobId 234&#58; Marking Volume "Week3-Tape001" in 
Error in Catalog.
31-May 23&#58;56 bacula-sd JobId 234&#58; Job 
BackupHomeDir.2010-05-31_23.48.54_04 waiting. Cannot find any appendable volum
es.
I can write to a newly initialised tape without problem, and can append so long 
as the PC is not rebooted - even after stopping & restarting Bacula.  Tapes are 
new, the btape test program runs 100% successfully and I can read from the 
tapes even after they are in error.

Tape device is Tandberg SLR7.  Driver options (set using mt) are: buffer-writes 
async-writes read-ahead two-fms can-bsr.  Device settings in bacula-sd.conf are:
&nbsp; &nbsp;Block Positioning = no
&nbsp; &nbsp;Hardware End of Medium = No # defaut is Yes
&nbsp; &nbsp;Backward Space Record = no
&nbsp; &nbsp;Backward Space File = no
&nbsp; &nbsp;Fast Forward Space File = No # This line required if above HEOM is 
set to "No"
&nbsp; &nbsp;BSF at EOM = Yes # Default is no
&nbsp; &nbsp;Two EOF = Yes #&nbsp; Minimum Block Size = 512


My backup schedule is weekly full, followed by nightly incremental.  Bacula 
version is 3.0.3.  OS is Fedora 12 (kernel 2.6.32.12-115.fc12.x86_64).

I have seen numerous postings about this on this forum & elsewhere - one post 
here had recommended settings which seemed to fix the problem for a few days 
before it resumed.  I have tried numerous combinations of driver and Bacula 
settings but always get this error (or a similar one with "MTEOF").  It seems 
the tape is either writing a marker it shouldn't, or *not* writing something it 
should, when the system is rebooted.  How do I correct the tape drive behaviour 
and/or configure Bacula to handle it?

Any ideas gratefully received.

Andrew

+----------------------------------------------------------------------
|This was sent by andrew AT wasielewski.co DOT uk via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------



------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
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>