Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 5 Nov 2002 11:10:28 -0500 (EST)
From:      "Julian C. Dunn" <jdunn@verticalscope.com>
To:        freebsd-stable@freebsd.org
Cc:        jmccormick@verticalscope.com
Subject:   SCSI tape drive problems with 4.7-STABLE
Message-ID:  <20021105110306.G93019-100000@anger.verticalscope.com>

next in thread | raw e-mail | index | archive | help
We recently upgraded our main workgroup server to 4.7-STABLE and tape
backups have started to fail recently. I turned on CAM debugging (of level
INFO) to see what is going on, and the following error messages are
showing up:

<thousands of lines of "enqueueing..." ellided -- I assume these are
normal status messages during the lifetime of the backup>
Nov  5 04:14:21 chrome /kernel: (sa0:sym0:0:6:0): sastrategy: enqueuing a
10240 variable byte write queue count now 1
Nov  5 04:14:21 chrome /kernel: (sa0:sym0:0:6:0): sastart(sa0:sym0:0:6:0):
Variable Record Count is 10240
Nov  5 04:14:21 chrome /kernel: (sa0:sym0:0:6:0): sastrategy: enqueuing a
10240 variable byte write queue count now 1
Nov  5 04:14:21 chrome /kernel: (sa0:sym0:0:6:0): sastart(sa0:sym0:0:6:0):
Variable Record Count is 10240
Nov  5 04:18:31 chrome /kernel: (noperiph:sym0:0:-1:-1): SCSI BUS reset
detected.
Nov  5 04:18:31 chrome /kernel: (sa0:sym0:0:6:0): Cam Status 0xe
Nov  5 04:18:31 chrome /kernel: (sa0:sym0:0:6:0): error 5 resid 10240
count 10240
Nov  5 04:18:31 chrome /kernel: (sa0:sym0:0:6:0): saclose(0): dev=0x0
softc=0x2c2d
Nov  5 04:18:31 chrome /kernel: (sa0:sym0:0:6:0): sastart(sa0:sym0:0:6:0):
CDB[0]=0x10 Key 0x6 ASC/ASCQ 0x29/0x0 CAM STATUS 0xc flags 0x0 resid 0
dxfer_len 0
Nov  5 04:18:31 chrome /kernel: (sa0:sym0:0:6:0): WRITE FILEMARKS. CDB: 10
0 0 0 1 0
Nov  5 04:18:31 chrome /kernel: (sa0:sym0:0:6:0): UNIT ATTENTION asc:29,0
Nov  5 04:18:31 chrome /kernel: (sa0:sym0:0:6:0): Power on, reset, or bus
device reset occurred
Nov  5 04:18:31 chrome /kernel: (sa0:sym0:0:6:0): failed to write terminating fi
lemark(s)
Nov  5 04:18:31 chrome /kernel: (sa0:sym0:0:6:0): sastart
Nov  5 04:19:31 chrome /kernel: sym0:6:control msgout: 80 6.
Nov  5 04:19:31 chrome /kernel: (sa0:sym0:0:6:0): Cam Status 0xb
Nov  5 04:19:45 chrome /kernel: (sa0:sym0:0:6:0): tape is now frozen- use
an OFFLINE, REWIND or MTEOM command to clear this state.


I'm wondering if this is indicative of a hardware problem, or whether it
is a software one. The drive is already an FRU but it was working
correctly up until the time we upgraded to 4.7 from 4.5. The drive is a

sa0: <ARCHIVE Python 06240-XXX 8160> Removable Sequential Access SCSI-3
device

attached to a

sym0: <875> port 0xc400-0xc4ff mem 0xda022000-0xda022fff,0xda021000-0xda0210ff irq 11 at device 17.0 on pci0
sym0: Tekram NVRAM, ID 7, Fast-20, SE, parity checking


The backup script is nothing more than a tar command with -f /dev/nsa0.

- Julian

--
Julian C. Dunn, B.A.Sc <jdunn@verticalscope.com>
Senior Software Developer, VerticalScope Inc.
Tel.: (416) 341-8950 x236  Fax: (416) 341-8959
WWW: www.verticalscope.com

"Windows NT encountered the following error:
The operation was completed successfully."



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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021105110306.G93019-100000>