Date: Sun, 12 Dec 1999 22:36:11 +0100 From: Martin Welk <mw@theatre.sax.de> To: Randy Bush <randy@psg.com> Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: filemarks? Message-ID: <19991212223611.A53246@theatre.sax.de> In-Reply-To: <E11xAe8-0002q1-00@rip.psg.com>; from randy@psg.com on Sun, Dec 12, 1999 at 07:10:48AM -0800 References: <E11wwsG-0001fn-00@rip.psg.com> <19991212082403.A34441@theatre.sax.de> <E11xAe8-0002q1-00@rip.psg.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Dec 12, 1999 at 07:10:48AM -0800, Randy Bush wrote:
> apologies for the typo. note that the `restore -s` did not work.
What a pity. Could have been very easy otherwise :-)
> here the problem report is with the problems in the problem report
> fixed. :-)
>
> btw, i suspect hardware. it's a bad scsi month for me.
Oh, one reason why I'm using FreeBSD for about five years it that real
problems already got usually fixed fast. When I started with FreeBSD,
the main reason was that I wanted to setup a CD-ROM server for the company
I was working for that time. Nobody had done that before, and when somebody
did so, it was very expensive, as Windows NT was available and needed much
resources, same with Netware and most other operating systems available. So
I chose a 486DX2/66 with 16 mbytes memory, one 540 mbyte SCSI disk, six
CD-ROM drives and the cheapest VGA card available (the machine was planned
to have a serial console shared with an Altos SVR3 machine) and the dealer
called me crazy. However, it worked fine, although some of the CD-ROMs I
was going to use were not ISO compliant, so a friend of mine in Dresden
(who brought FreeBSD to me and me to FreeBSD) helped me with some kernel
patch and I was happy again.
Okay, back from travelling in time (I was reading the 300 bit/s acoustic
coupler thread on freebsd-isdn before) to your problem.
> what am i misunderstanding here?
I am absolutely not sure if my idea could be the right one, I haven't used
such a tape drive before - we've always chosen the Tandberg SLR during the
last two years. But with one of the last ones (a SLR6 one, now known as
SLR24 as Tandberg is changing their way of naming tapes from increasing
numbers to using the ``compression enabled optimum tape size'', because
that drive does 12 gb uncompressed and up to 24 gb compressed) I had some
difficulties, two, and thanks to Matt Dillon for helping me.
Usually, there are two filemarks written to the tape, but there are devices
``that can only write 1'' (man page for mt, there is furtter informations).
You could try ``mt geteotmodel'' to see what's the driver's opinion about
which model it uses currently.
Next thing: use the other one - see at the seteotmodel option and do some
``mt seteotmodel n'' (where n is 1 or 2) and look if something is changing.
In /sys/cam/scsi/scsi_sa.c (sa driver source) it reads
{
{ T_SEQUENTIAL, SIP_MEDIA_REMOVABLE, "HP",
"T20*", "*"}, SA_QUIRK_FIXED|SA_QUIRK_1FM, 512
},
This is the only quirk for HP tapes, and your's won't be matched against it
as T503 won't match T20* - maybe, it has something to do with it.
May be some of the SCSI gurus can help better.
Regards,
Martin
--
/| /| | /| / ,,You know, there's a lot of opportunities,
/ |/ | artin |/ |/ elk if you're knowing to take them,
you know, there's a lot of opportunities,
Freiberg/Saxony, Germany if there aren't you can make them,
mw@sax.de / mw@theatre.sax.de make or break them!'' (Tennant/Lowe)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991212223611.A53246>