From owner-freebsd-hackers Fri Jun 28 12:21:53 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DFDD837B401 for ; Fri, 28 Jun 2002 12:21:23 -0700 (PDT) Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CC1B43E12 for ; Fri, 28 Jun 2002 12:21:08 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: from panzer.kdm.org (localhost [127.0.0.1]) by panzer.kdm.org (8.12.5/8.12.5) with ESMTP id g5SJL7Ki004174; Fri, 28 Jun 2002 13:21:07 -0600 (MDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.12.5/8.12.5/Submit) id g5SJL71G004173; Fri, 28 Jun 2002 13:21:07 -0600 (MDT) (envelope-from ken) Date: Fri, 28 Jun 2002 13:21:07 -0600 From: "Kenneth D. Merry" To: Dirk-Willem van Gulik Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: How noisy should ch(4) be ? Message-ID: <20020628132107.A4107@panzer.kdm.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from dirkx@webweaving.org on Fri, Jun 28, 2002 at 08:36:16AM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Jun 28, 2002 at 08:36:16 +0000, Dirk-Willem van Gulik wrote: > > On a stock 4.5-RELEASE I get *lots* of > > Jun 28 11:37:53 amanda /kernel: ch: warning: could not map element source > address 40384d to a valid element type > > as soon as chio touches the tape changer. > > How noisy should ch(4) be - is this normal ? Previous experience with a > SONY DAT library and a seagate was more silent :-) It probably means the changer is doing something bogus. Specifically, it has said that the source address for a particular element is valid, but the source element address doesn't map to any known component in the changer. (picker, portal, slot, drive) You can try several things here: - run 'chio ielem' before you do anything. This may make the changer look at what it has, and perhaps figure out that it doesn't really have a source addresses for various elements. - try moving every tape in the changer to some destination and back. The fastest thing to do, if the changer supports it, would probably be moving the tapes to the picker and then back to a slot. - comment out the warning in copy_element_status(). - see if there is updated firmware for the changer. > Device details: > > camcontrol devlist > at scbus0 target 4 lun 0 (pass0,sa0) > at scbus0 target 5 lun 0 (pass1,sa1) > at scbus0 target 6 lun 0 (pass2,ch0) > > dmesg > Waiting 5 seconds for SCSI devices to settle > sa0 at ahc0 bus 0 target 4 lun 0 > sa0: Removable Sequential Access SCSI-2 device > sa0: 10.000MB/s transfers (10.000MHz, offset 15) > sa1 at ahc0 bus 0 target 5 lun 0 > sa1: Removable Sequential Access SCSI-2 device > sa1: 10.000MB/s transfers (10.000MHz, offset 15) > ch0 at ahc0 bus 0 target 6 lun 0 > ch0: Removable Changer SCSI-2 device > ch0: 3.300MB/s transfers > ch0: 28 slots, 2 drives, 1 picker, 1 portal > > kernel config > > # cat AMANDA > .. > device ahc # AHA2940 and onboard AIC7xxx devices > device scbus # SCSI bus (required) > device sa # Sequential Access (tape etc) > device ch # SCSI media changers > > thanks ! Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message