Just for grins and giggles, try cleaning your drive several times.
On 6/29/2011 12:39 AM, Christian Tardif wrote:
On 23/06/2011 10:06, Brian Debelius wrote:
I
found something strange. If I try to issue this command:
2011/6/29 Christian Tardif
> **
> On 23/06/2011 10:06, Brian Debelius wrote:
>
> I found something strange. If I try to issue this command:
>
> mt -f /dev/nst0 status
>
> I'll get one line that says:
>
> Tape block size 0 bytes. Density code 0x81 (DLT 15GB compressed).
>
> Isn't that strange? I'm
On 23/06/2011 10:06, Brian Debelius wrote:
I
found something strange. If I try to issue this command:
mt -f /dev/nst0 status
I'll get one line that says:
Tape block size 0 bytes. Density code 0x81 (DLT 15GB
co
On 6/21/2011 10:57 PM, Christian Tardif wrote:
I found something strange. If I try to issue this command:
mt -f /dev/nst0 status
I'll get one line that says:
Tape block size 0 bytes. Density code 0x81 (DLT 15GB compressed).
Isn't that strange? I'm trying to understand what this density code
On 21/06/2011 14:20, John Drescher wrote:
I believe the only way that can happen (if you are in the correct tape
density mode)
I found something strange. If I try to issue this command:
mt -f /dev/nst0 status
I'll get one line that says:
>> No difference at all.
>
> So why are both, at the evidence, acting differently?
>
I do not know.
>
>>> >
>>> > II'll try to force the maximum size of the tape in the config but I
>>> > would
>>> > have to put it over 80GB limit if I only want the hardware compression
>>> > to be useful. Not s
On 21/06/2011 20:57, John Drescher wrote:
>> So, since btape comes from Bacula, I assume that, in some way, Bacula
>> > should be able to write to my VXA-2 tape a more or less 80GB of data. So
>> > what's the difference between bacula-sd's way of accessing the tape and
>> > btape's way?
>> >
> N
> So, since btape comes from Bacula, I assume that, in some way, Bacula
> should be able to write to my VXA-2 tape a more or less 80GB of data. So
> what's the difference between bacula-sd's way of accessing the tape and
> btape's way?
>
No difference at all.
>
> II'll try to force the maximum si
On 21/06/2011 19:33, ganiuszka wrote:
> You can use vxaTool to diagnostic purpose for your tape drive. There
> is option (from vxaTool readme file):
>
> -t [W/R/F] (optional)
> Test write/read functionality of the device.
>
> Optional [R]ead-only, [W]rite-only and [F]ull-tape flags
> **
2011/6/21 Christian Tardif :
> Hi,
>
> I have a VXA-2 tape used with X23 tapes (replacement for V23 tapes)
> that should backup 80GB Uncompressed. Bacula stops after an average of
> 27GB, stating that the media is full. It seems that tapeinfo thinks
> that it has 80GB available (see below).
>
> H
On Tue, Jun 21, 2011 at 2:11 PM, Christian Tardif
wrote:
>
> On 21/06/2011 13:01, John Drescher wrote:
>
> Look for scsi errors in your dmesg. Bacula will assume it hits the end
> of the tape when it hits any write error.
>
> Don't have any SCSI error on dmesg. It really looks like Bacula thinks t
On 21/06/2011 13:01, John Drescher wrote:
Look for scsi errors in your dmesg. Bacula will assume it hits the end
of the tape when it hits any write error.
Don't have any SCSI error on dmesg. It really looks like Bacula
thinks that it can only write 30GB of
On Tue, Jun 21, 2011 at 12:48 PM, Christian Tardif
wrote:
> Hi,
>
> I have a VXA-2 tape used with X23 tapes (replacement for V23 tapes)
> that should backup 80GB Uncompressed. Bacula stops after an average of
> 27GB, stating that the media is full. It seems that tapeinfo thinks
> that it has 80G
13 matches
Mail list logo
