I runned the btape cap :
phoenix:/etc/bacula# btape /dev/st0
Tape block granularity is 1024 bytes.
btape: butil.c:258 Using device: "/dev/st0" for writing.
btape: btape.c:335 open_dev /dev/st0 OK
*cap
Configured device capabilities:
EOF BSR BSF FSR FSF FASTFSF !BSFATEOM EOM REM !RACCESS !AUTOMOUNT !LABEL
!ANONVOLS ALWAYSOPEN
Device status:
OPENED TAPE !LABEL MALLOC APPEND !READ !EOT !WEOT !EOF !NEXTVOL !SHORT
Device parameters:
Device name: /dev/st0
File=0 block=0
Min block=0 Max block=0
Status:
Bacula status: file=0 block=0
Device status: BOT ONLINE IM_REP_EN file=0 block=0
btape: btape.c:1707 Device status: 645. ERR=
I think it's going to require more information to isolate it. Have you
used the drive with other software and verified that it works properly?
it worked fine with Amanda. I didn't tried with other softwares ...
Phil Stracchino wrote:
Julien Cigar wrote:
Did you use the cap command to list tape capabilities? Did you run a
fill test to ensure that Bacula can fill up a tape and write on to the
next? There are several capabilities that are crucial for Bacula.
I runned all the tests which are in the documentation and they completed
successfully.
What is the 'cap' command you are talking about ... ?
Run btape, and type 'help'. It'll show you all the commands, including
this one:
cap list device capabilities
Do all backups fill a tape, or does this occur only when you completely
fill a tape?
it occurs randomly, sometimes after 10go, sometimes at the end, ...
I think it's going to require more information to isolate it. Have you
used the drive with other software and verified that it works properly?
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
