When you refer to patch 108725, what patch are you referring to? In
other words, is this a Solaris OS patch, or a NetWorker patch? We're
running Redhat Linux on our storage node and Solaris on our primary
server, and we, too, were experiencing these "positioning by record
disabled" messages on our LTO devices managed by the storage node server
before adding a proper st.conf file. After adding the st.conf file, the
problems went away, but we're still running 6.1.1. Will we not need to
woory about needing this file if we upgrade to 6.1.3?
Thanks.
George Sinclair
George.Sinclair AT noaa DOT gov
Howard Martin wrote:
>
> I can comment on a couple of the points (see below) as we were getting
> similar problems on 6.1.2 using LTO drives (not a problem when we were
> using DLT700's)
> a.
> 6.1.3 upgrade reduced problems significantly but not completely.
> b.
> The recent versions of patch 108725 have the LTO drives built in to st so
> you don't need to have an entry in st.conf - st.conf entries supercede the
> inbuilt ones but when I tested them I could not find any improvement by
> playing with them.
> c.
> The IBM drivers interfere with the normal Solaris tape drivers and usually
> the only reason for using them is that they come out before Sun upgrades
> theirs.
>
> On Tue, 4 Mar 2003 11:06:56 -0500, Jon Hickmott <jonny AT UWO DOT CA> wrote:
>
> >> Another ideas
> >>
> >> 1 Upgrade to 6.1.3
> >>
> >> If you can't : on the server (and storage node eventually)
> >> # touch /nsr/debug/noimmediate
> >> then stop and restart NetWorker
> >>
> >> 3 Verify your LTO conf in the /kernel/drv/st.conf
> >>
> >
> >Can You be specific on what the entries should be in this file for IBM LTO
> Fibre
> >attached tape drives. Currently I have the default st.conf file which came
> from
> >the patch 108725-11 and it does not even list IBM LTO devices. I believe
> these are
> >compiled into the st driver but I don't know what they are or should be.
> >
> >>
> >> 4 Don't use the IBM Lto Driver for Solaris
> >
> >Why? Have you had bad experiences with this driver? This is one of the
> options I
> >was going to try hoping it would in the least give me the ability to talk
> to the
> >drives and retrieve error info directly.
> >
> >Thanks,
> >Jon
> >
> >--
> >Note: To sign off this list, send a "signoff networker" command via email
> >to listserv AT listmail.temple DOT edu or visit the list's Web site at
> >http://listmail.temple.edu/archives/networker.html where you can
> >also view and post messages to the list.
> >=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
> --
> Note: To sign off this list, send a "signoff networker" command via email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can
> also view and post messages to the list.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
