We're using Bacula 1.36.3 (yea, I know - old) on CentOS 3 (yea, I know -
old) with AIT3 tapes (which store about 150 GB each) in an 8-tape
changer (Sony Stor-Station LIB-81).
Suddenly, Bacula has started marking tapes as 'Full' when only a few
files have been written to them and only a few GB. We haven't changed
anything on the system or any settings recently. Below are examples of
what I'm seeing on three of the tapes that Bacula has marked as Full:
Tape 1: 10,788,852,486 | 12 files - about 10-11 GB
Tape 2: 1,026,192,264 | 1 file - about 1 GB
Tape 3: 5,899,324,539 | 25 files - about 6 GB
Having used Bacula for a while, I know these tapes hold much more data
than that and this is absolutely not right.
These are previously used Bacula tapes which have had the index erased
(weof). We recycle them after a period of time, but have never had a
problem with this. In my syslog file I see:
pr 11 01:46:39 stash st0: Error with sense data: Info fld=0x1b, Current
st09:00: sense key Medium Error
Apr 11 01:46:39 stash Additional sense indicates Write error
I can see that the drive doesn't like the tapes but am not sure why it
suddenly can't write to them beyond a certain point. Anyone have any
possible explanations for this?
--
Deann Corum
System Administrator
Nicholas School of the Environment and Earth Sciences
919-613-8148
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
