Thanks Jean, that was it. The tape drives themselves are /dev/nst0 and
/dev/nst1. I've got amtapetype working now, excellent. I'm trying to figure
out how to get the specifics on the different device modes (i.e.
/dev/nst0a, etc), but if I need help I'll make a separate post.
-M
On Tue, Jan 28, 2014 at 6:23 PM, Jean-Louis Martineau
<martin...@zmanda.com>wrote:
> /dev/sg2 is the changer device not the tape device, what is the tape
> device? It is a /dev/nst? device
>
>
>
> On 01/28/2014 05:54 PM, Michael Stauffer wrote:
>
>> Tom and Jon, thanks for the great replies. I'm just getting back to this
>> project again.
>>
>> I've tried this
>>
>> amtapetype -f -b 524288 -t IBM-ULTRIUM-TD5 /dev/sg2 2>&1 | tee
>> tapetype-ultrium-512k-block
>>
>> and get this
>>
>> amtapetype: Error writing label 'amtapetype-1614155207': File
>> /dev/sg2 is not a tape device at /usr/sbin/amtapetype line 93.
>>
>> I figure I need to define a tape device that includes /dev/sg2? I've
>> added the changer definition to amanda.conf:
>>
>> define changer scalar_i500 {
>> tpchanger "chg-robot:/dev/sg2"
>> property "tape-device" "0=tape:/dev/sg2"
>> }
>> tpchanger "scalar_i500"
>>
>> But am getting the same error. I've also tried
>>
>> amtapetype -f -b 524288 -t IBM-ULTRIUM-TD5 scalar_i500
>>
>> and get
>>
>> amtapetype: Error writing label 'amtapetype-1739790301': Can't
>> open tape device scalar_i500: No such file or directory at
>> /usr/sbin/amtapetype line 93.
>>
>> mtx works fine on /dev/sg2. Any suggestions? Thanks.
>>
>> -M
>>
>>
>> On Thu, Jan 16, 2014 at 7:31 PM, Tom Robinson
>> <tom.robin...@motec.com.au<mailto:
>> tom.robin...@motec.com.au>> wrote:
>>
>> On 17/01/14 10:55, Jon LaBadie wrote:
>> > On Thu, Jan 16, 2014 at 06:04:14PM -0500, Michael Stauffer wrote:
>> >> Hi,
>> >>
>> >> I'm setting up amanda 3.3.4. I can't find a definiton for
>> changer's drives
>> >> (IBM ULTRIUM-TD5 LTO-5) in /etc/amanda/template.d/tapetypes
>> >>
>> >> Can someone point me to a source for this, or to where I can
>> learn how to
>> >> determine the params I need for the drives? Thanks
>> >>
>> > The command amtapetype should be in your amanda server installation.
>> > It can be used to determine the values for your site.
>> >
>> > The only tapetype parameter amanda actually uses is capacity.
>> > So you could hand create a definition and be close enough
>> > for government work.
>> >
>> > Jon
>>
>> Created on OmniOS v11 r151006:
>>
>> $ amtapetype -f -b 524288 -t ULT3580-TD5 /dev/rmt/0b 2>&1 | tee
>> /etc/opt/csw/amanda/weekly/tapetype-512k-block
>> Checking for FSF_AFTER_FILEMARK requirement
>> Applying heuristic check for compression.
>> Wrote random (uncompressible) data at 85721088 bytes/sec
>> Wrote fixed (compressible) data at 295261525.333333 bytes/sec
>> Compression: enabled
>> Writing one file to fill the volume.
>> Wrote 1519480995840 bytes at 85837 kb/sec
>> Got LEOM indication, so drive and kernel together support LEOM
>> Writing smaller files (15194390528 bytes) to determine filemark.
>> device-property "FSF_AFTER_FILEMARK" "false"
>> define tapetype ULT3580-TD5 {
>> comment "Created by amtapetype; compression enabled"
>> length 1483868160 kbytes
>> filemark 868 kbytes
>> speed 85837 kps
>> blocksize 512 kbytes
>> }
>> # for this drive and kernel, LEOM is supported; add
>> # device-property "LEOM" "TRUE"
>> # for this device.
>>
>> I ran amtapetype for a number of different block sizes (32k, 256k,
>> 512k and 2048k) but I found that
>> block sizes over 512 kbytes gave me driver issues and no LEOM
>> capability. My amdump reports show
>> fairly reasonable tape streaming speeds:
>>
>> Avg Tp Write Rate (k/s) 143476 143842 5723.0
>>
>> If you have a different system just run amtapetype and be patient.
>> It will be worth the wait.
>>
>> Regards,
>> Tom
>>
>> Tom Robinson
>> IT Manager/System Administrator
>>
>> MoTeC Pty Ltd
>>
>> 121 Merrindale Drive
>> Croydon South
>> 3136 Victoria
>> Australia
>>
>> T: +61 3 9761 5050
>> F: +61 3 9761 5051
>> E: tom.robin...@motec.com.au <mailto:tom.robin...@motec.com.au>
>>
>>
>>
>>
>>
>
