Hi,
I think I have a faulty tape or two. What is the best recommended way of
testing this? Generate a file from /dev/urandom, write it to the tape and
md5sum it?
Also, what is the expected lifetime for Travan 4 tapes (each used once a
week)? When should I retire them?
..Brian
--
Init System
On Saturday 31 August 2002 07:45, Brian Jonnes wrote:
>Hi,
>
>I think I have a faulty tape or two. What is the best recommended
> way of testing this? Generate a file from /dev/urandom, write it
> to the tape and md5sum it?
Most drives do the equ of that themselves. its when they can't
recover t
On Sat, Aug 31, 2002 at 01:45:44PM +0200, Brian Jonnes wrote:
> Hi,
>
> I think I have a faulty tape or two. What is the best recommended way of
> testing this? Generate a file from /dev/urandom, write it to the tape and
> md5sum it?
>
If you use software compression with Amanda, one easy way
On Sat 31 Aug 02 16:11, Gene Heskett wrote:
> On Saturday 31 August 2002 07:45, Brian Jonnes wrote:
> >Hi,
> >
> >I think I have a faulty tape or two. What is the best recommended
> > way of testing this? Generate a file from /dev/urandom, write it
> > to the tape and md5sum it?
>
> Most drives do
On Sunday 01 September 2002 10:09, Brian Jonnes wrote:
>On Sat 31 Aug 02 16:11, Gene Heskett wrote:
>> On Saturday 31 August 2002 07:45, Brian Jonnes wrote:
>> >Hi,
>> >
>> >I think I have a faulty tape or two. What is the best
>> > recommended way of testing this? Generate a file from
>> > /dev/u
--On Sunday, September 01, 2002 16:09:59 +0200 Brian Jonnes <[EMAIL PROTECTED]> wrote:
> ---
> These dumps were to tape DAILY_04.
> The next tape Amanda expects to use is: DAILY_05.
>
>
> STATISTICS:
> Total Full Daily
> --
On Sun 01 Sep 02 20:51, Gene Heskett wrote:
> Thats just a wee bit more than my tapetype says it is here, I got
> 3780mb as the capacity.
Odd.
> What version of amanda? There was a period of a couple of weeks
> where the internal rewind function was a bit foobar. The tape
> might not have been
On Monday 02 September 2002 02:24, Brian Jonnes wrote:
>On Sun 01 Sep 02 20:51, Gene Heskett wrote:
>> Thats just a wee bit more than my tapetype says it is here, I
>> got 3780mb as the capacity.
>
>Odd.
No, not really. It just demonstrates that the marketing weenies
tend to round things off to
I think I'm getting closer to the problem. First off, it seems that ide-tape
doesn't work properly with the Colorado drives. I haven't yet had time to
test, but I'll install ide-scsi when I next get a chance.
Does anyone know of a reference as to the differences between ide-tape/ide
and st/ide
> -Original Message-
> From: Dietmar Goldbeck [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, August 31, 2002 10:20 AM
> To: Brian Jonnes
> Cc: [EMAIL PROTECTED]
> Subject: Re: Testing tapes
>
>
> On Sat, Aug 31, 2002 at 01:45:44PM +0200, Brian Jonnes wrote:
> &
Hi!
I'm using amanda 2.4.4p1 in combination with a Quantum SDLT 320
tape drive. This week I received some replacement tapes for broken
ones.
Using the first tape I got some kind of "short write" while using
amflush:
[...]
*** A TAPE ERROR OCCURRED: [[writing file: Input/output error]].
[...]
x
On Sunday 23 November 2003 04:28, Martin Oehler wrote:
>Hi!
>
>I'm using amanda 2.4.4p1 in combination with a Quantum SDLT 320
>tape drive. This week I received some replacement tapes for broken
>ones.
>
>Using the first tape I got some kind of "short write" while using
>amflush:
>[...]
>*** A TAPE
Hi!
Am So, 2003-11-23 um 14.16 schrieb Gene Heskett:
> There is amtapetype, which will destructively write the tape till it
> hits EOT, and will tell you the size it found. See the man page for
> running options to help speed it up as its quite slow, doing 2
> passes.
SYNOPSIS
amtapety
Martin Oehler wrote:
Hi!
Am So, 2003-11-23 um 14.16 schrieb Gene Heskett:
There is amtapetype, which will destructively write the tape till it
hits EOT, and will tell you the size it found. See the man page for
running options to help speed it up as its quite slow, doing 2
passes.
SYNOPSIS
On Monday 24 November 2003 03:46, Martin Oehler wrote:
>Hi!
>
>Am So, 2003-11-23 um 14.16 schrieb Gene Heskett:
>> There is amtapetype, which will destructively write the tape till
>> it hits EOT, and will tell you the size it found. See the man
>> page for running options to help speed it up as i
On Mon, Nov 24, 2003 at 09:46:31AM +0100, Martin Oehler wrote:
> Hi!
>
> Am So, 2003-11-23 um 14.16 schrieb Gene Heskett:
> > There is amtapetype, which will destructively write the tape till it
> > hits EOT, and will tell you the size it found. See the man page for
> > running options to help
On Mon, Nov 24, 2003 at 09:46:31AM +0100, Martin Oehler wrote:
> Hmm, the only option that sounds like it could speed up the [amtapetype] process
> is blocksize. Does anyone know a good value for this?
The same value as amdump will be using! With some tape
technologies, the tape's capacity depen
Hi!
Am Mo, 2003-11-24 um 13.54 schrieb Gene Heskett:
> On Monday 24 November 2003 03:46, Martin Oehler wrote:
[...]
> Doing this to a tape also should tell you whether or not the drives
> internal compression is in use, which for amanda, should be turned
> off as that hides the true size of the
Hi!
Am Mo, 2003-11-24 um 23.30 schrieb Eric Siegerman:
> On Mon, Nov 24, 2003 at 09:46:31AM +0100, Martin Oehler wrote:
> > Hmm, the only option that sounds like it could speed up the [amtapetype] process
> > is blocksize. Does anyone know a good value for this?
>
> The same value as amdump will
On Tue, Nov 25, 2003 at 10:46:10AM +0100, Martin Oehler wrote:
> Hi!
>
> Am Mo, 2003-11-24 um 13.54 schrieb Gene Heskett:
> > On Monday 24 November 2003 03:46, Martin Oehler wrote:
>
> [...]
> > Doing this to a tape also should tell you whether or not the drives
> > internal compression is in us
On Mon, Nov 24, 2003 at 10:23:12AM +0100, Paul Bijnens wrote:
>
> Read on a few lines further in the man page. The most important
> parameter for speed is the estimated size. It's the stop/start when
> writing a filemark that slows down the most. The default estimated
> size is 1 Gbyte. Amtape
Jon LaBadie wrote:
Might it be a good idea to have amtapetype note too many files
being written during the first phase and taking some action?
Maybe with an option to override the checking.
My idea was to write only one large file in the first pass, just
until it hits end of tape. Then rewind and
On Mon, Nov 24, 2003 at 07:14:56PM +0100, Paul Bijnens wrote:
> Jon LaBadie wrote:
>
> >Might it be a good idea to have amtapetype note too many files
> >being written during the first phase and taking some action?
> >Maybe with an option to override the checking.
>
> My idea was to write only on
On Mon, Nov 24, 2003 at 07:14:56PM +0100, Paul Bijnens wrote:
> My idea was to write only one large file in the first pass, just
> until [amtapetype] hits end of tape.
One problem with that is that the drive's internal buffering
might distort the results, by letting amtapetype think it has
success
24 matches
Mail list logo
