Thanks, I believe that I actually did try a dump that way.
Will have to check the case notes but believe it was an
SGI reportable issue.
I don't recall if I said in my first letter yesterday but there
is currently an open SGI case, it was they that had initially
asked about label vs xfer to tape
I said I'd check this in the docs that came wth out DLT8000.
There's a couple of pages about hooking up a DLT to an IRIX box, but upon
closer reading the book only offers instructions for DLT devices upto a
DLT7000 not for a DLT8000 ... ;(
Kind regards,
--
Gerhard den Hollander
Gerhard,
In order to run the DLT8000 on irix (pre-6.5.12) I did modify
the device tables, changed the device recognition string but
didn't mess with the parameters so the DLT8000 was treated as
a 7000.
Mods where to the /var/sysgen/master.d/scsi file.
SGI suggested I might do this under 6.5.12
* Brian Cuttler <[EMAIL PROTECTED]> (Thu, Aug 02, 2001 at 11:13:44AM -0400)
> Gerhard,
> In order to run the DLT8000 on irix (pre-6.5.12) I did modify
> the device tables, changed the device recognition string but
> didn't mess with the parameters so the DLT8000 was treated as
> a 7000.
> Mods w
* Brian Cuttler <[EMAIL PROTECTED]> (Wed, Aug 01, 2001 at 10:41:55AM -0400)
> John,
> No hardware changes, problems began with the OS upgrade, checked
> all the cables. We can actually perform amdump just fine as long
> as the tape was labeled before the OS upgrade.
> Yes, amanda hitting the ten
* John R. Jackson <[EMAIL PROTECTED]> (Wed, Aug 01, 2001 at 09:15:32AM -0500)
>>I do not know the mechanism for "labeling" but wanted to
>>describe the process for SGI. ...
> The sequence is (and yes, all those rewinds look a bit silly now that
> I write it all down :-):
> open
> rewind
>
For what it's worth, I haven't seen this with my tape drive yet, but my
old Indigo began having some SCSI buss timeouts and errors on the
external cdrom after upgrading to 6.5.12m. I checked the comp.sys.sgi*
newsgroups and didn't see anything there yet about it. It may be a
driver issue with th
John,
No hardware changes, problems began with the OS upgrade, checked
all the cables. We can actually perform amdump just fine as long
as the tape was labeled before the OS upgrade.
Yes, amanda hitting the tender spots as opposed to Amanda being
the problem. I'm trying to make that exact point
>I meant I believe that our version which is 2.4.2p2 was current.
>
>The query was on "current" rather than the version number I reported.
If I understand what you're asking, yes, 2.4.2p2 is the current stable
release. There have been some patches since then, but nothing in the
tape area (or at
>We are seeing bus errors and timeouts that we didn't see
>under the earlier version of IRIX.
Ah, I see.
Amanda is a purely application level program that makes normal system
calls. It cannot be the cause of these types of errors, although it might
instigate them (along the lines of a text edit
John,
We are seeing bus errors and timeouts that we didn't see
under the earlier version of IRIX.
I can pull the errors from the SYSLOG file if you'd like.
I was trying though to figure out, and relay the info to SGI,
why label was failing and writing the dumps was working. I
don't have enough
>Unfortunately we are unable to label the tape # amlabel -f
>at any either 35gig or 40 gig density. ...
Ummm, that's not anywhere near enough information to go on. What version
of Amanda? What, exactly did you put on the command line? What did
it say? Why do you think it didn't work?
>I do
Hello amanda users,
We have been supporting our DLT8000 by treating it as a DLT7000
under IRIX 6.5.(3-7)m and modifying the scsi device tables.
We recently upgraded to 6.5.12m which "supports" DLT8000 via
the new "ts" class device driver.
Unfortunately we are unable to label the tape # amlabel
13 matches
Mail list logo
