Amanda-Users

Re: Onstream ADR50 Block Size

2003-04-11 01:50:39
Subject: Re: Onstream ADR50 Block Size
From: Gene Heskett <gene.heskett AT verizon DOT net>
To: Matt Hyclak <hyclak AT math.ohiou DOT edu>, amanda-users AT amanda DOT org
Date: Fri, 11 Apr 2003 00:24:10 -0400
On Thu April 10 2003 22:25, Matt Hyclak wrote:
>On Fri, Apr 11, 2003 at 01:15:26AM -0000, rwk AT americom DOT com 
enlightened us:
>> I am trying to run amanda 2.4.2 on Linux RH8.0 using an Onstream
>> ADR50 drive.
>>
>> I am having problems and I have tracked it down to a variable
>> block size issue.  for example, if I do the following:
>>
>>      mt -f /dev/nst0 setblk 0
>
>My device for this drive is /dev/nosst0, not /dev/nst0. Could that
> be the problem?

I'd not think so Matt.  While I have no first hand knowledge about 
that /dev/nosst0 device, but my *SWAG says that devices useage will 
call in some code to deal with the OnStream drives, some of which 
have been what we could call 'problem children' in the past.  Thats 
based on the added 'os' for OnStream in the devices english 
language nameing.

Besides if I was going to do a setblk 0, to me it would makes ense 
to use the device intended, not /dev/nst0.

However, this is all just a *Scientific Wild Assed Guess, and I 
could well be full of it...  Ymmv in other words :)

-- 
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz  512M
99.26% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.