From owner-freebsd-hackers  Sun Mar  7 18: 4: 9 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from absinthe.shenton.org (Absinthe.Shenton.Org [209.31.147.194])
	by hub.freebsd.org (Postfix) with ESMTP id 6A81C14D9E
	for <hackers@freeBSD.org>; Sun,  7 Mar 1999 18:04:03 -0800 (PST)
	(envelope-from chris@shenton.org)
Received: (from chris@localhost)
	by absinthe.shenton.org (8.9.1/8.9.1) id VAA14818;
	Sun, 7 Mar 1999 21:03:44 -0500 (EST)
To: hackers@freeBSD.org
Subject: 3.1-STABLE: nrsa0 T4000 doesn't honor "no rewind"? SCSI errs in logs
X-Emacs: Emacs 20.3, MULE 4.0 (HANANOEN)
MIME-Version: 1.0 (generated by SEMI 1.8.5 - "Nishi-Takaoka")
Content-Type: text/plain; charset=US-ASCII
From: Chris Shenton <chris@shenton.org>
Date: 07 Mar 1999 21:03:43 -0500
Message-ID: <877lsslou8.fsf@absinthe.shenton.org>
Lines: 44
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Been trying to use both Amanda and a simple script to dump my local
filesystems to a HP Colorado T4000 Travan-4 SCSI tape drive,
/dev/nrsa0.  It appears to NOT be honoring the "no rewind" device and
therefore rewinding and overwriting all earlier files. This breaks
backups, etc.

Doing simple Amanda "amlabel" talks to nrsa0 OK but it appears to read
the tape, rewind, write the amanda label (file 1), rewind AGAIN, and
then store the first filesystem template (file 2).  But the second
rewind causes file 2 to overwrite file 1.  It acts like it's not
honoring the "no rewind" flag.

Doing something simpler -- a little script which loops over my local
filesystems and does a dump to nrst0 -- has similar behavior.  It
dumps /, /var, /usr, and /home each time rewinding between dumps thus
overwriting the previous filesystem image.

I finally discovered in /var/log/messages errors like:
 
Mar  7 20:10:01 Thanatos /kernel: (sa0:ahc0:0:5:0): SPACE. CDB: 11 1 ff ff ff 0
Mar  7 20:10:01 Thanatos /kernel: (sa0:ahc0:0:5:0): ILLEGAL REQUEST asc:2c,0
Mar  7 20:10:01 Thanatos /kernel: (sa0:ahc0:0:5:0): Command sequence error
Mar  7 20:10:01 Thanatos /kernel: (sa0:ahc0:0:5:0): unable to backspace over one of double filemarks at EOD- opting for safety
Mar  7 20:35:56 Thanatos /kernel: (sa0:ahc0:0:5:0): SPACE. CDB: 11 1 ff ff ff 0
Mar  7 20:35:56 Thanatos /kernel: (sa0:ahc0:0:5:0): ILLEGAL REQUEST asc:2c,0
Mar  7 20:35:56 Thanatos /kernel: (sa0:ahc0:0:5:0): Command sequence error
Mar  7 20:35:56 Thanatos /kernel: (sa0:ahc0:0:5:0): unable to backspace over one of double filemarks at EOD- opting for safety

And I see these times correlate with the times my script goes to dump
the next filesystem:

    # /sbin/dump 0aubf 128 /dev/nrsa0 /usr
      DUMP: Date of this level 0 dump: Sun Mar  7 20:10:01 1999
      DUMP: level 0 dump on Sun Mar  7 20:10:01 1999
      [...]
      DUMP: Closing /dev/nrsa0
    # /sbin/dump 0aubf 128 /dev/nrsa0 /home
      DUMP: Date of this level 0 dump: Sun Mar  7 20:35:56 1999

I believe I had this T4000 drive working fine back on 2.2.8-STABLE. 
Anything I can do to debug the problem? Makes it pretty useless for
backups. :-(

Thanks.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message