On Wed, Feb 26, 2003 at 09:54:00AM -0000, Nigel Barker wrote:
>
> >Thought 2. you did not say if you had a changer, make, model, /dev entry.
> If not, you needn't use any changer entries
>
> Overland XB with a DLT700 drive.
> dlt /dev/rmt/1n (I've had the tape respond to this, so i know its right)
Well, at least it works. Does rmt/0 also work (say with tar or dd)?
> changer /dev/sq/c3t610 (created using Veritas stuff, I can't vouch for
> it)
Guessing here, "sq == sequential", which is one of the sgen driver types.
An c3tXXX sounds like "c == controller 3", "t == target XXX", but certainly
not target 610 as the target generally means scsi id, like 0-15. Are you
sure that is not c3t6d0 (target 6 device, i.e. lun, 0).
But the location is not what I've seen. What is /dev/sq/c3t610, a device,
a symlink (to what?)? Is there a /dev/scsi/sequential/* with maybe the same
information? How about /dev/changer/?
>
> >Thought 3. you have changerfile set to chg-multi. that would suggest your
> tpchanger should also be chg-multi
>
> Done that, now "playing" with the chg-multi.conf file
I should have written they need to match, not that you should choose chg-multi.
"multi" is meant for "multi"ple drives, not for a changer.
> >Thought 4. for my Solaris system and drive chg-mtx worked fine. others
> have used chg-zd-mtx (note you will have to obtain and install mtx). Still
> others have configured the "sgen" (generic scsi?) driver and used chg-scsi,
> or the chg-mtx's
>
> I explored mtx and sgen, and was unable to get either to create a device for
> me.
Not surprising that mtx didn't create a device. It doesn't. It operates
on a changer device. Maybe your /dev/sq/* device.
> >Thought 5. /dev/rmt/1n ? Do you have another tape drive at 0?
>
> /dev/rmt/1n responds as the tape drive, but I don't have anything I can get
> to respond at /dev/rmt/0n, even though all the files are there in /dev/rmt/
> Is this something I should investigate, or can I ignore them?
Do you only have one tape drive/changer? Is other software going to be
screwed up in some important way if the device names change? If only 1
and no other software problems, you could get a complete device reconfiguation
and likely move the drive to drive 0, removing all else. The stuff in
/dev/rmt are just symlinks to stuff in /devices.
A device reconfiguration at reboot would entail "touch /reconfigure" and reboot
or at boot time, at the ok prompt, do a "b -r" (boot -r).
Sometimes old stuff keeps reappearing. If so, rm all the /devices/.../*st*
(st == scsi tape, or is it sequential tape) devices that are pointed to from
/dev/rmt and all the /dev/rmt links. Then either the reconfiguration reboot
or read up on devfsadm to recreate the devices without reboot. The deprecated,
obscelescent command "tapes" would also do the same device recreation I think.
> >Thought 6. the device /dev/rmt/1n is choosing the "default" density and/or
> compression for your tape drive.
> If that is what you want, fine, otherwise check into 1ln, 1mn, ...
>
> Ah, wondered what they all were!
> I'll investigate, thanks for the "heads up"
prtconf -v will give lots of output including some stuff about "st" devices.
Included will be what tape device(s) it recognizes at boot time. From this
you can get pointers into the /kernel/drv/st.conf file to explore further
the entries for that kind of tape drive.
--
Jon H. LaBadie jon AT jgcomp DOT com
JG Computing
4455 Province Line Road (609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
|
