From owner-freebsd-scsi Mon Oct 26 17:04:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17312 for freebsd-scsi-outgoing; Mon, 26 Oct 1998 17:04:03 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17307 for ; Mon, 26 Oct 1998 17:04:00 -0800 (PST) (envelope-from ken@plutotech.com) Received: (from ken@localhost) by pluto.plutotech.com (8.8.7/8.8.5) id SAA18934; Mon, 26 Oct 1998 18:02:48 -0700 (MST) From: Kenneth Merry Message-Id: <199810270102.SAA18934@pluto.plutotech.com> Subject: Re: Problem with cdrecord in 3.0-RELEASE, and few other questions... In-Reply-To: <9144.981027@nstl.nnov.ru> from Alexander Dubinin at "Oct 27, 98 03:27:42 am" To: alex@nstl.nnov.ru Date: Mon, 26 Oct 1998 18:02:48 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Alexander Dubinin wrote... > Hello All! > > Question 1: > > Some time ago I install 3.0-RELEASE to my computer with RICOH MP6200S, > and NCR 53c810A SCSI adapter (Used for CD-recording). > > Then I use 2.2.6-STABLE - all works fine, I link /dev/scgx to > /dev/rcd0.ctl, and all 'll Ok. > Now, in 3.0, I can't find this entry. In hints to cdrecord written, > that I can use /dev/cd0a directly, with CAM support. > So, how can I do it? > > Can anybody help? When you're running cdrecord under CAM, there are several things to keep in mind: - you must have the pass(4) device configured in your kernel. (i.e. "device pass0" in your config file) - you need one pass device node in /dev for each SCSI device in your system. If you've got 10 SCSI devices, you'd type: cd /dev sh MAKEDEV pass10 - You need the transport layer device as well: cd /dev sh MAKEDEV xpt1 The xpt(4) device is automatically enabled when you have SCSI configured in your kernel, so there is no need for a separate xpt device line in your kernel config file. [ Note: If you installed 3.0 from the standard distribution (i.e. not via cvsup and buildworld/installworld), you should already have the xpt device and several pass devices in /dev ] - specify your CD recorder by bus/target/lun. I don't think the code to specify devices by name works with CAM. To find out what bus/target/lun your CD recorder is on, type "camcontrol devlist". - There is no need for the /dev/scgx symlink under CAM. cdrecord doesn't use that at all. > Question 2: > On other my computer (proxy server, with AHA 2940 and two Conner > drives) periodically such messages appears: > > (da1:ahc0:0:1:0): tagged openings now 32 > (da1:ahc0:0:1:0): tagged openings now 31 > > etc. > That does this mean? Is it dangerous for my disks/controller, or not? It isn't dangerous at all, and is actually quite normal. It means that your disk has enough space to hold 31 transactions at a time. You can use the above numbers to compare the various disks you have, and see which ones support the most tagged transactions. > Question 3: > > And, while rebooting or halting system: > > syncing disks... 4 4 done > (da0:ahc0:0:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 > (da0:ahc0:0:0:0): ILLEGAL REQUEST asc:20,0 > (da0:ahc0:0:0:0): Invalid command operation code field replaceable unit: 14 > > And there are no disk on bus 0, lun 0 and id 0 !!!! > Why system try to synchronize it? That's a good question. Can you send me the output of 'camcontrol devlist -v' for that system? Are you *sure* you're running 3.0-RELEASE? There were some changes that went in a couple of days before the release to disable error messages when the cache sync operation returns illegal request. i.e., if you're running 3.0-RELEASE, you shouldn't see that error message at all. If you are running 3.0-RELEASE, and you still see that message, it means that there's a bug somewhere or other. In any case, that error message is quite harmless, and it's nothing to be concerned about. I would like to know why it's popping up, though. :) Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message