>>>>> On Mon, 22 Jan 2007 13:41:38 +0100, Jose Molina said:
> 
> Hi there,
> 
> After last time recomendations to change our drive config under FreeBSD,
> doing the usual btape tests all seemed fine and was working, but after a
> few days running, volumes are starting to fail with this error:
> 
> 18-Jan 15:04 rap-sd: Volume "DiarioXALOC-02" previously written, moving
> to end of data.
> 18-Jan 15:04 rap-sd: srvbanyalbufar.2007-01-18_15.00.00 Error: I cannot
> write on Volume "DiarioXALOC-02" because:
> The number of files mismatch! Volume=5 Catalog=4
> 18-Jan 15:04 rap-sd: Marking Volume "DiarioXALOC-02" in Error in
> Catalog.
> 
> I've added "/usr/bim/mt -f /dev/nsa0 seteotmodel 1" when the system
> starts like suggested.
> 
> My drive configuration:
> 
> Device {
>   Name = Drive-1                      #
>   Drive Index = 0
>   Media Type = LTO2
>   Archive Device = /dev/nsa0
>   AutomaticMount = yes;               # when device opened, read it
>   AlwaysOpen = yes;
>   RemovableMedia = yes;
>   RandomAccess = no;
>   AutoChanger = yes
> 
>   Offline On Unmount = no
>   Hardware End of Medium = no
> }

It might be useful to find out what that tape contains by doing

bls -c bacula-sd.conf -j -V'*' /dev/nsa0

(you'll have to unmount it from bconsole first and then load the tape manually
in your autochanger).

Also, the output of

select * from jobmedia
 where mediaid=(select mediaid from media where volumename='DiarioXALOC-02')
 order by startfile;

would tell is what Bacula thinks it contains.

__Martin

-------------------------------------------------------------------------
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