Am Montag, 15. Mai 2006 18:33 schrieben Sie:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Did you ever do the 'btape' tests that are discussed in the manual and
> tune your Device spec based on the returns from that command?
^
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Did you ever do the 'btape' tests that are discussed in the manual and
tune your Device spec based on the returns from that command?
_ _ _ _ ___ _ _ _
|Y#| | | |\/| | \ |\ | | |Ryan Novosielski - User Support Spec. III
|$&| |__| | | |
On Thu, 13 Oct 2005, Phil Stracchino wrote:
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?
While you're looking at the hardware
Am Donnerstag, 13. Oktober 2005 08:50 schrieb Julien Cigar:
> Hello,
>
> sometimes I have "write error" messages during my full backup (on tapes) :
>
> 12-Oct 18:44 phoenix-sd: BebifFullBackup.2005-10-12_06.00.00 Error:
> block.c:552 Write error at 15:111 on device /dev/st0. ERR=Input/output
> erro
Josh Fisher wrote:
> I have occasional problems with Sony AIT drives on 2940UW controllers. I
> believe it's the tape drive that gets confused, because when it happens,
> ("it" being the drive stops communicating), even a reboot of the server
> doesn't fix the problem when the drive is left powered
I have occasional problems with Sony AIT drives on 2940UW controllers. I
believe it's the tape drive that gets confused, because when it happens,
("it" being the drive stops communicating), even a reboot of the server
doesn't fix the problem when the drive is left powered on. Power cycling
the
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 !AUTOMOUN
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
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.
Julien Cigar wrote:
> Thanks for replying
>
> The tape is:
>
> phoenix:/var/backups# cat /proc/scsi/scsi
> Attached devices:
> Host: scsi0 Channel: 00 Id: 01 Lun: 00
> Vendor: SONY Model: SDX-500C Rev: 010f
> Type: Sequential-AccessANSI SCSI revision: 02
>
> and t
Thanks for replying
The tape is:
phoenix:/var/backups# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: SONY Model: SDX-500C Rev: 010f
Type: Sequential-AccessANSI SCSI revision: 02
and the controller is:
phoenix:/var/backups#
Julien Cigar wrote:
> Hello,
>
> sometimes I have "write error" messages during my full backup (on tapes) :
>
> 12-Oct 18:44 phoenix-sd: BebifFullBackup.2005-10-12_06.00.00 Error:
> block.c:552 Write error at 15:111 on device /dev/st0. ERR=Input/output
> error.
> 12-Oct 18:44 phoenix-sd: BebifFul
12 matches
Mail list logo
