From owner-freebsd-scsi Sun Nov 15 06:59:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA01137 for freebsd-scsi-outgoing; Sun, 15 Nov 1998 06:59:08 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from math.berkeley.edu (math.Berkeley.EDU [128.32.183.94]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA01132 for ; Sun, 15 Nov 1998 06:59:07 -0800 (PST) (envelope-from dan@math.berkeley.edu) Received: (from dan@localhost) by math.berkeley.edu (8.8.7/8.8.7) id GAA26354; Sun, 15 Nov 1998 06:58:44 -0800 (PST) Date: Sun, 15 Nov 1998 06:58:44 -0800 (PST) From: dan@math.berkeley.edu (Dan Strick) Message-Id: <199811151458.GAA26354@math.berkeley.edu> To: freebsd-scsi@FreeBSD.ORG Subject: bug in cam_real_open_device() Cc: dan@math.berkeley.edu Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In file: camlib.c,v 1.2 1998/10/12 21:54:00 ken Exp beginning at line 587: if ((fd = open(path, flags)) < 0) { sprintf(cam_errbuf, "%s: couldn't open passthrough device %s\n" "%s: %s", func_name, newpath, func_name, strerror(errno)); goto crod_bailout; } The bug is that "newpath" hasn't been filled in at this point. Another bug is that since the contents of newpath is unknown, cam_errbuf might not be large enough (resulting in buffer overflow). --------------------------------------- I feel compelled to express severe irritation with this part of the cam design. The above code is trying to open one of the passthrough devices. It determines the passthough device name by issuing a CAMGETPASSTHRU ioctl() to the xpt device that maps driver name and unit number into a passthrough driver name and unit number. These driver names are not names in /dev but names defined in kernel source driver tables that happen (by design of course) to correspond to names of special files in /dev. For example, "/dev/rda0s1c" refers to driver "da" unit "0" and "/dev/pass1" refers to driver "pass" unit "1". The cam library has to make the invalid assumption that special file names correspond to kernel driver names and has couple of special rules for two well known cases that break this assumption ("sd" and "st"). The cam library is effectively assuming that names in /dev are compiled into the kernel. In general, I think it is a very serious error for the kernel to contain hardwired file names. The only name that the kernel really has to know is "/sbin/init" and that name should be passed to it as an argument during bootstrap. There are a lot of little glitchy consequences of this aspect of the cam design. For example, cam_open_device() will fail if the required passthrough device has not been created in /dev, but there is currently no way for a program using camlib to determine the name of the required passthough device until after camlib has successfully opened it. (The camlib routines happen not to fill in this cam_device struct member until after the open succeeds. There is no camlib routine that does just the CAMGETPASSTHRU ioctl(). Since the CAMGETPASSTHRU ioctl() is undocumented, using it on the side is not an option.) As a consequence, my program cannot produce an error message telling the user that he has to create a specific passthrough device in /dev. This is a real bummer. This whole issue would never have come up and most of camlib would be obviously vacuous if SCSI ioctl()s could be issued via the usual device special files instead of the /dev/pass files. What exactly do the /dev/pass files do that could not have been done with the real device special files? (I.E. Why can't we just do SCSI passthough ioctl()s using the raw disk devices like we used to?) Dan Strick dan@math.berkeley.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Nov 15 09:37:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA15889 for freebsd-scsi-outgoing; Sun, 15 Nov 1998 09:37:48 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA15882 for ; Sun, 15 Nov 1998 09:37:46 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id KAA13368; Sun, 15 Nov 1998 10:30:36 -0700 (MST) Date: Sun, 15 Nov 1998 10:30:36 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199811151730.KAA13368@narnia.plutotech.com> To: dan@math.berkeley.edu (Dan Strick) cc: scsi@FreeBSD.ORG Subject: Re: bug in cam_real_open_device() X-Newsgroups: pluto.freebsd.scsi In-Reply-To: <199811151458.GAA26354@math.berkeley.edu> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-BETA (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <199811151458.GAA26354@math.berkeley.edu> you wrote: > > In file: camlib.c,v 1.2 1998/10/12 21:54:00 ken Exp > beginning at line 587: > > if ((fd = open(path, flags)) < 0) { > sprintf(cam_errbuf, "%s: couldn't open passthrough device %s\n" > "%s: %s", func_name, newpath, func_name, > strerror(errno)); > goto crod_bailout; > } > > The bug is that "newpath" hasn't been filled in at this point. > Another bug is that since the contents of newpath is unknown, > cam_errbuf might not be large enough (resulting in buffer overflow). File a PR. I'm sure Ken will fix this later today, but it's always a good idea to put bugs in the database. > I feel compelled to express severe irritation with this part of the > cam design. The userland library is "sugar coating" on the ioctls provided by CAM. It was written to serve the developers immediate needs to port certain software and the interfaces it exports are by no means cast in stone. > The above code is trying to open one of the passthrough > devices. It determines the passthough device name by issuing a > CAMGETPASSTHRU ioctl() to the xpt device that maps driver name and > unit number into a passthrough driver name and unit number. These > driver names are not names in /dev but names defined in kernel source > driver tables that happen (by design of course) to correspond to names > of special files in /dev. For example, "/dev/rda0s1c" refers to > driver "da" unit "0" and "/dev/pass1" refers to driver "pass" > unit "1". > > The cam library has to make the invalid assumption that special > file names correspond to kernel driver names and has couple of > special rules for two well known cases that break this assumption > ("sd" and "st"). The cam library is effectively assuming that names > in /dev are compiled into the kernel. > > In general, I think it is a very serious error for the kernel to contain > hardwired file names. The only name that the kernel really has to know > is "/sbin/init" and that name should be passed to it as an argument > during bootstrap. This has been discussed on -scsi before, so you may want to look in the archives to see all of the details of this problem. Sure, you can kill all hard coded tables of device names in the kernel, but you will eventually need to do some device resolution based on that device's canonical name. Take booting as an example. We can either look for the root device based on it's canonical name (the name the driver for that device knows itself as), or we can have hard coded tables that we use to perform the translation from name to major/minor number, and use that mechanism. Since the intended goal is to get rid of major and minor numbers once DEVFS is useful (next year probably), and major and minor numbers are harder for the end user to deal with than canonical names (Hmm, do I need to boot off 0x3040 or was that 0x2030?) we should be removing as much dependence on them as possible. With DEVFS, the device node you open can be called whatever you want since the filesystem has recorded the information required to get to the device you want to deal with, so major/minor number or name translation isn't a problem. But this somewhat skirts around your real issue. > There are a lot of little glitchy consequences of this aspect of the > cam design. For example, cam_open_device() will fail if the required > passthrough device has not been created in /dev, but there is currently > no way for a program using camlib to determine the name of the required > passthough device until after camlib has successfully opened it. > (The camlib routines happen not to fill in this cam_device struct > member until after the open succeeds. There is no camlib routine > that does just the CAMGETPASSTHRU ioctl(). Since the CAMGETPASSTHRU > ioctl() is undocumented, using it on the side is not an option.) It is supposed to be documented. File a PR. > This whole issue would never have come up and most of camlib would > be obviously vacuous if SCSI ioctl()s could be issued via the > usual device special files instead of the /dev/pass files. > What exactly do the /dev/pass files do that could not have been > done with the real device special files? (I.E. Why can't we just > do SCSI passthough ioctl()s using the raw disk devices like we > used to?) You're missing a fundamental design concept in CAM. The pass-thru device and the 'real' device are completely separate entities. They know nothing about each other and don't need to in order to function correctly. Why is this the case? Think of the requirements for the cd driver. It can't do anything useful if it doesn't have media. So it's open routine will fail if no media is in the drive. This simplifies the tracking of internal state in the driver since the only place were this check needs to occur is in the open routine. Now fold in the 'pass-thru' capability to this driver and you add unnecessary complexity. The conditions for which the device must allow an open change. There are also issues concerning how per-transaction resource scheduling is performed that need to be addressed. Blech. CAM already provideds for multiple 'peripheral drivers' to have instances accessing the same underlying device (For instance a 'probe' driver, CD driver and a WORM driver), so it becomes very natural to push pass-thru functionality into its own driver. To present your kind of world view, each peripheral driver would need to understand that pass-thru activity is possible and likely perform a device table lookup on each transaction to forward it to the appropriate pass-thru instance. Blech. If you want a reliable way to get to the pass-thru driver, have your users specify the Bus, Target, Lun of the device they want to talk to, and use the appropriate method in the CAM library to open the device using that information. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Nov 15 15:41:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA18153 for freebsd-scsi-outgoing; Sun, 15 Nov 1998 15:41:46 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA18148 for ; Sun, 15 Nov 1998 15:41:44 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id QAA23512; Sun, 15 Nov 1998 16:41:17 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199811152341.QAA23512@panzer.plutotech.com> Subject: Re: bug in cam_real_open_device() In-Reply-To: <199811151458.GAA26354@math.berkeley.edu> from Dan Strick at "Nov 15, 98 06:58:44 am" To: dan@math.berkeley.edu (Dan Strick) Date: Sun, 15 Nov 1998 16:41:17 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (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 Dan Strick wrote... > > In file: camlib.c,v 1.2 1998/10/12 21:54:00 ken Exp > beginning at line 587: > > if ((fd = open(path, flags)) < 0) { > sprintf(cam_errbuf, "%s: couldn't open passthrough device %s\n" > "%s: %s", func_name, newpath, func_name, > strerror(errno)); > goto crod_bailout; > } > > The bug is that "newpath" hasn't been filled in at this point. > Another bug is that since the contents of newpath is unknown, > cam_errbuf might not be large enough (resulting in buffer overflow). Yep, it's a bug. I just checked in fixes; get version 1.4 of camlib.c > I feel compelled to express severe irritation with this part of the > cam design. [ complaints essentially about using /dev/pass* instead of the 'normal' device nodes ] Since Justin covered most of your comments, I'll just say one or two things here. > There are a lot of little glitchy consequences of this aspect of the > cam design. For example, cam_open_device() will fail if the required > passthrough device has not been created in /dev, but there is currently > no way for a program using camlib to determine the name of the required > passthough device until after camlib has successfully opened it. > (The camlib routines happen not to fill in this cam_device struct > member until after the open succeeds. There is no camlib routine > that does just the CAMGETPASSTHRU ioctl(). Since the CAMGETPASSTHRU > ioctl() is undocumented, using it on the side is not an option.) > As a consequence, my program cannot produce an error message > telling the user that he has to create a specific passthrough > device in /dev. This is a real bummer. The fact that the CAMGETPASSTHRU ioctl isn't documented is probably a bug. Just like the fact that none of the CCB types are documented is a bug. We didn't have time before 3.0 went out to document everything, and we still don't have much time. (Justin and I are both very busy with "real" work, which at the moment doesn't include CAM work.) I think it would probably be better to use the XPT_DEV_MATCH CCB. It performs device matching functions in a much more general way than the CAMGETPASSTHRU ioctl. (Which, in retrospect, probably should have been implemented as another CCB type. I think I had a reason at one point for a separate ioctl, but I can't remember what it was now.) As Justin mentioned, the CAM library is just "sugar coating" on top of the regular ioctls/CCBs. You can use the ioctls directly, if it makes your job easier. If you want to determine whether the user has the necessary passthrough device created in /dev, I would suggest doing the following: - Assuming you have the device name (e.g. "da" or "cd") and unit number of the device the user wants to talk to: - send an XPT_DEV_MATCH CCB with the device name and unit number, and set it up to match against the device name and unit number. - you will receive the bus, target and lun for that particular device when the CCB returns. - now, send another XPT_DEV_MATCH CCB. Specify the bus/target/lun for the device that you got from the last CCB, and specify the device name "pass". - you will receive the unit number for the passthrough device that you want to open. You can also just issue the CAMGETPASSTHRU ioctl, which will do the same thing more or less. There are two different versions of the ioctl, one that gets called when you go through the transport layer device, and the other when you go through one of the 'normal' devices. If you're going to use that ioctl, I would recommend using the one in the transport layer (/dev/xpt0) device. This is because when you use the one that's available via the regular devices, you have to go through that device's open routine. The open routine may not succeed in all cases. (This gets back to the reason we went with a separate passthrough device as opposed to integrating the ioctls in the standard device nodes. Justin covered that pretty well in his mail.) If you'd like to make a CAM library function that checks for the existence of a passthrough device for a given "regular" device or bus/target/lun, feel free to send me the diffs. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Nov 15 15:45:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA18506 for freebsd-scsi-outgoing; Sun, 15 Nov 1998 15:45:08 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA18497 for ; Sun, 15 Nov 1998 15:45:03 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id QAA23532; Sun, 15 Nov 1998 16:44:36 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199811152344.QAA23532@panzer.plutotech.com> Subject: Re: Support for Mylex Flashpoint Adapters? In-Reply-To: from "Andreas S. Wetzel" at "Nov 14, 98 10:41:41 pm" To: mickey@deadline.snafu.de (Andreas S. Wetzel) Date: Sun, 15 Nov 1998 16:44:36 -0700 (MST) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (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 Andreas S. Wetzel wrote... > Recently I was wondering if the bt driver in FreeBSD 3.0-RELEASE supports the > Mylex (aka Buslogic) BT-930/BT-950 (Flashpoint) series of host adapters. Nope, they aren't supported in any version of FreeBSD. > The > heading of all relevant files do only list the BT-956/BT-958 (MultiMaster) > hostadapters, but the file /sys/pci/bt_pci.c defines a > PCI_DEVICE_ID_BUSLOGIC_FLASHPOINT macro which seems otherwise unused? I wouldn't draw any conclusions from that. > Are there concrete plans for supporting the flashpoint adapters? Justin has been planning on updating the buslogic driver to support the Flashpoint cards. The Mylex people promised him boards, but so far they haven't delivered. I think he's making other arrangements to get the cards. > Are they downward compatible to the MultiMaster Adapters? I don't think they're compatible. > Also I would be interested in the technical details and differences between > the MultiMaster and Flashpoint adapters. Does anyone have experiences with > these controllers using FreeBSD? Well, no one has experience using the Flashpoint adapters under FreeBSD. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Nov 15 17:23:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA28647 for freebsd-scsi-outgoing; Sun, 15 Nov 1998 17:23:39 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from news2.du.gtn.com (news2.du.gtn.com [194.77.9.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA28641 for ; Sun, 15 Nov 1998 17:23:36 -0800 (PST) (envelope-from ticso@cicely5.cicely.de) Received: from cicely.cicely.de (cicely.de [194.231.9.142]) by news2.du.gtn.com (8.8.6/8.8.6) with ESMTP id CAA04147 for ; Mon, 16 Nov 1998 02:22:52 +0100 (MET) Received: from cicely5.cicely.de (cicely5.cicely.de [10.1.1.7]) by cicely.cicely.de (8.8.8/8.8.8) with ESMTP id CAA17454 for ; Mon, 16 Nov 1998 02:22:57 +0100 (CET) Received: (from ticso@localhost) by cicely5.cicely.de (8.9.0/8.9.0) id CAA00857; Mon, 16 Nov 1998 02:22:47 +0100 (CET) Message-ID: <19981116022247.23622@cicely.de> Date: Mon, 16 Nov 1998 02:22:47 +0100 From: Bernd Walter To: freebsd-scsi@FreeBSD.ORG Subject: 520byte sector size Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org da8 at ahc6 bus 0 target 3 lun 0 da8: Fixed Direct Access SCSI2 device da8: 5.0MB/s transfers (5.0MHz, offset 12) da8: 388MB (782600 520 byte sectors: 64H 32S/T 382C) FreeBSD don't like this sector size very much :( I know that they can be formated with 512 byte sectors. I've done this with an old 1542 on a similar drive. I just selected format in the BIOS-Tool and it lowlevel formated it with 512 byte sectors. Unfortunately I don't like the idea of plugging a videocard into this host just for waiting for each drive (6 ones) I've tried: camcontrol cmd -n pass -u 12 -v -t 9999 -c "4 0 0 0 0 0" but I gave me a fresh formated 520byte HDD :( does anybody know the command to change the sector size? -- B.Walter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Nov 15 18:46:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA04760 for freebsd-scsi-outgoing; Sun, 15 Nov 1998 18:46:31 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA04755 for ; Sun, 15 Nov 1998 18:46:30 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id TAA24619; Sun, 15 Nov 1998 19:45:53 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199811160245.TAA24619@panzer.plutotech.com> Subject: Re: 520byte sector size In-Reply-To: <19981116022247.23622@cicely.de> from Bernd Walter at "Nov 16, 98 02:22:47 am" To: ticso@cicely.de (Bernd Walter) Date: Sun, 15 Nov 1998 19:45:53 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (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 Bernd Walter wrote... > da8 at ahc6 bus 0 target 3 lun 0 > da8: Fixed Direct Access SCSI2 device > da8: 5.0MB/s transfers (5.0MHz, offset 12) > da8: 388MB (782600 520 byte sectors: 64H 32S/T 382C) > > FreeBSD don't like this sector size very much :( > I know that they can be formated with 512 byte sectors. > I've done this with an old 1542 on a similar drive. > I just selected format in the BIOS-Tool and it lowlevel > formated it with 512 byte sectors. > > Unfortunately I don't like the idea of plugging a videocard > into this host just for waiting for each drive (6 ones) > > I've tried: > camcontrol cmd -n pass -u 12 -v -t 9999 -c "4 0 0 0 0 0" > but I gave me a fresh formated 520byte HDD :( > > does anybody know the command to change the sector size? Well, I've never done it before, but you might try changing the "Data Bytes per Physical Sector" field in mode page 3 (the "Format device" page). Of the two disks in my machine here, the Quantum doesn't allow changing that value, but the IBM apparantly does. If you can change it, you can then probably try formatting the drive again. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Nov 15 23:22:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA00451 for freebsd-scsi-outgoing; Sun, 15 Nov 1998 23:22:23 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA00440 for ; Sun, 15 Nov 1998 23:22:19 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id IAA03514; Mon, 16 Nov 1998 08:21:55 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id IAA11923; Mon, 16 Nov 1998 08:19:51 +0100 (MET) (envelope-from j) Message-ID: <19981116081950.08123@uriah.heep.sax.de> Date: Mon, 16 Nov 1998 08:19:50 +0100 From: J Wunsch To: freebsd-scsi@FreeBSD.ORG Cc: Bernd Walter Subject: Re: 520byte sector size Reply-To: Joerg Wunsch References: <19981116022247.23622@cicely.de> <199811160245.TAA24619@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199811160245.TAA24619@panzer.plutotech.com>; from Kenneth D. Merry on Sun, Nov 15, 1998 at 07:45:53PM -0700 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Kenneth D. Merry wrote: > > does anybody know the command to change the sector size? > Well, I've never done it before, but you might try changing the > "Data Bytes per Physical Sector" field in mode page 3 (the "Format > device" page). This once also worked for a Seagate drive for me. The other option i've seen (ISTR it was an IBM drive) was to change the `block size' parameter in the buffer header of a MODE SELECT command, and then reformat the drive. I don't know whether there's an easy opportunity to do this using camcontrol, short of manually assembling a complete MODE SELECT command using -c. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Nov 15 23:26:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA01155 for freebsd-scsi-outgoing; Sun, 15 Nov 1998 23:26:34 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from news2.du.gtn.com (news2.du.gtn.com [194.77.9.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA01150 for ; Sun, 15 Nov 1998 23:26:31 -0800 (PST) (envelope-from ticso@cicely5.cicely.de) Received: from cicely.cicely.de (cicely.de [194.231.9.142]) by news2.du.gtn.com (8.8.6/8.8.6) with ESMTP id IAA24842; Mon, 16 Nov 1998 08:25:54 +0100 (MET) Received: from cicely5.cicely.de (cicely5.cicely.de [10.1.1.7]) by cicely.cicely.de (8.8.8/8.8.8) with ESMTP id IAA18859; Mon, 16 Nov 1998 08:26:13 +0100 (CET) Received: (from ticso@localhost) by cicely5.cicely.de (8.9.0/8.9.0) id IAA01015; Mon, 16 Nov 1998 08:26:05 +0100 (CET) Message-ID: <19981116082604.51678@cicely.de> Date: Mon, 16 Nov 1998 08:26:04 +0100 From: Bernd Walter To: "Kenneth D. Merry" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: 520byte sector size References: <19981116022247.23622@cicely.de> <199811160245.TAA24619@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199811160245.TAA24619@panzer.plutotech.com>; from Kenneth D. Merry on Sun, Nov 15, 1998 at 07:45:53PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Nov 15, 1998 at 07:45:53PM -0700, Kenneth D. Merry wrote: > Bernd Walter wrote... > > da8 at ahc6 bus 0 target 3 lun 0 > > da8: Fixed Direct Access SCSI2 device > > da8: 5.0MB/s transfers (5.0MHz, offset 12) > > da8: 388MB (782600 520 byte sectors: 64H 32S/T 382C) > > > > FreeBSD don't like this sector size very much :( > > I know that they can be formated with 512 byte sectors. > > I've done this with an old 1542 on a similar drive. > > I just selected format in the BIOS-Tool and it lowlevel > > formated it with 512 byte sectors. > > > > Unfortunately I don't like the idea of plugging a videocard > > into this host just for waiting for each drive (6 ones) > > > > I've tried: > > camcontrol cmd -n pass -u 12 -v -t 9999 -c "4 0 0 0 0 0" > > but I gave me a fresh formated 520byte HDD :( > > > > does anybody know the command to change the sector size? > > Well, I've never done it before, but you might try changing the "Data Bytes > per Physical Sector" field in mode page 3 (the "Format device" page). > That's all I get: root@cicely5# camcontrol modepage -n pass -u 12 -e -m 3 -P 3 camcontrol: error sending mode sense command Some other pages are working fine. > Of the two disks in my machine here, the Quantum doesn't allow changing > that value, but the IBM apparantly does. On my DCAS Drives I can at least take a look on these pages... Does anybody know what the adaptec controler does when low-level formating a drive. > > If you can change it, you can then probably try formatting the drive again. > > Ken > -- > Kenneth Merry > ken@plutotech.com -- B.Walter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 16 00:19:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA06501 for freebsd-scsi-outgoing; Mon, 16 Nov 1998 00:19:00 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA06494 for ; Mon, 16 Nov 1998 00:18:58 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id BAA26903; Mon, 16 Nov 1998 01:18:22 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199811160818.BAA26903@panzer.plutotech.com> Subject: Re: 520byte sector size In-Reply-To: <19981116081950.08123@uriah.heep.sax.de> from J Wunsch at "Nov 16, 98 08:19:50 am" To: joerg_wunsch@uriah.heep.sax.de Date: Mon, 16 Nov 1998 01:18:22 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG, ticso@cicely.de X-Mailer: ELM [version 2.4ME+ PL28s (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 J Wunsch wrote... > As Kenneth D. Merry wrote: > > > > does anybody know the command to change the sector size? > > > Well, I've never done it before, but you might try changing the > > "Data Bytes per Physical Sector" field in mode page 3 (the "Format > > device" page). > > This once also worked for a Seagate drive for me. The other option > i've seen (ISTR it was an IBM drive) was to change the `block size' > parameter in the buffer header of a MODE SELECT command, and then > reformat the drive. I don't know whether there's an easy opportunity > to do this using camcontrol, short of manually assembling a complete > MODE SELECT command using -c. There isn't an easy option to edit the mode page header, or block descriptor from camcontrol. The only way to do it would be the "long" way. (You could also write a C program to do it.) Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 16 10:07:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA09788 for freebsd-scsi-outgoing; Mon, 16 Nov 1998 10:07:49 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from jli.com (jli.com [199.2.111.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA09768 for ; Mon, 16 Nov 1998 10:07:36 -0800 (PST) (envelope-from trost@cloud.rain.com) Received: (qmail 19393 invoked by uid 4); 16 Nov 1998 18:06:39 -0000 Received: (qmail 28672 invoked from network); 16 Nov 1998 17:58:00 -0000 Received: from localhost.cloud.rain.com (HELO cloud.rain.com) (127.0.0.1) by localhost.cloud.rain.com with SMTP; 16 Nov 1998 17:58:00 -0000 To: Joerg Wunsch Subject: Re: tape hang problem Cc: scsi@FreeBSD.ORG References: <19981115083147.59967@uriah.heep.sax.de> <466.911090634@cloud.rain.com> In-reply-to: Your message of Sun, 15 Nov 1998 08:31:47 +0100. <19981115083147.59967@uriah.heep.sax.de> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <28656.911239079.1@cloud.rain.com> Date: Mon, 16 Nov 1998 09:57:59 -0800 Message-ID: <28663.911239079@cloud.rain.com> From: Bill Trost Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org J Wunsch writes: As Bill Trost wrote: > When the system hangs, it prints several messages like the following on > the console: > > (da0:ahc0:0:0:...) SCB 0x11 - timed out in datain phase, SCSISIGI == 0x44 > SEQADDR == 0x110, > SSTATI == 0x2 I've seen such behaviour (incidentally also on an Archive Python) for a tape where i ultimately found that the drive that recorded the tape has too much adjustment tolerance to my own tape drive. That seems unlikely, as it is the "same" tape drive (although it has been to the shop in Okie City since the tape was written). Apparently, the drive then can't read the requested block immediately, and starts retensioning the tape (as i would guess from the sound). That's not my failure mode. Everything goes silent when my tape drive acts up. Another datum: I can successfuly "mt fsr" past the bad record and read the rest of the tape. (That's how I found out the data I'm looking for isn't on this tar backup... )-: ) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 16 12:13:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA02917 for freebsd-scsi-outgoing; Mon, 16 Nov 1998 12:13:06 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from silver.gn.iaf.nl (silver.gn.iaf.nl [193.67.144.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA02912 for ; Mon, 16 Nov 1998 12:13:04 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by silver.gn.iaf.nl (8.8.8/8.8.8) with SMTP id VAA19874; Mon, 16 Nov 1998 21:12:38 +0100 Received: by uni4nn.gn.iaf.nl with UUCP id AA11945 (5.67b/IDA-1.5); Mon, 16 Nov 1998 20:44:45 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id UAA01018; Mon, 16 Nov 1998 20:01:39 +0100 (CET) From: Wilko Bulte Message-Id: <199811161901.UAA01018@yedi.iaf.nl> Subject: Re: 520byte sector size In-Reply-To: <199811160245.TAA24619@panzer.plutotech.com> from "Kenneth D. Merry" at "Nov 15, 98 07:45:53 pm" To: ken@plutotech.com (Kenneth D. Merry) Date: Mon, 16 Nov 1998 20:01:39 +0100 (CET) Cc: ticso@cicely.de, freebsd-scsi@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (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 As Kenneth D. Merry wrote... > Bernd Walter wrote... > > da8 at ahc6 bus 0 target 3 lun 0 > > da8: Fixed Direct Access SCSI2 device > > da8: 5.0MB/s transfers (5.0MHz, offset 12) > > da8: 388MB (782600 520 byte sectors: 64H 32S/T 382C) > > > > FreeBSD don't like this sector size very much :( > > I know that they can be formated with 512 byte sectors. > > I've done this with an old 1542 on a similar drive. > > I just selected format in the BIOS-Tool and it lowlevel > > formated it with 512 byte sectors. > > > > Unfortunately I don't like the idea of plugging a videocard > > into this host just for waiting for each drive (6 ones) > > > > I've tried: > > camcontrol cmd -n pass -u 12 -v -t 9999 -c "4 0 0 0 0 0" > > but I gave me a fresh formated 520byte HDD :( > > > > does anybody know the command to change the sector size? > > Well, I've never done it before, but you might try changing the "Data Bytes > per Physical Sector" field in mode page 3 (the "Format device" page). > > Of the two disks in my machine here, the Quantum doesn't allow changing > that value, but the IBM apparantly does. FWIW I also once succeeded in setting a Micropolis from 518 to 512 bytes/sec. > If you can change it, you can then probably try formatting the drive again. You need a format yes. Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 16 13:53:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20396 for freebsd-scsi-outgoing; Mon, 16 Nov 1998 13:53:21 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from math.berkeley.edu (math.Berkeley.EDU [128.32.183.94]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20387 for ; Mon, 16 Nov 1998 13:53:19 -0800 (PST) (envelope-from dan@math.berkeley.edu) Received: (from dan@localhost) by math.berkeley.edu (8.8.7/8.8.7) id NAA14263; Mon, 16 Nov 1998 13:52:48 -0800 (PST) Date: Mon, 16 Nov 1998 13:52:48 -0800 (PST) From: dan@math.berkeley.edu (Dan Strick) Message-Id: <199811162152.NAA14263@math.berkeley.edu> To: joerg_wunsch@uriah.heep.sax.de Subject: Re: 520byte sector size Cc: dan@math.berkeley.edu, freebsd-scsi@FreeBSD.ORG, ticso@cicely.de Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > This once also worked for a Seagate drive for me. The other option > i've seen (ISTR it was an IBM drive) was to change the `block size' > parameter in the buffer header of a MODE SELECT command, and then I believe the correct method is to change the "data bytes per phys sector" parameter (bytes 12 and 13, big endian) on the "format parameter page" (page code 3) immediately before reformatting. > reformat the drive. I don't know whether there's an easy opportunity > to do this using camcontrol, short of manually assembling a complete > MODE SELECT command using -c. I have a program that lets you manually edit individual fields of mode pages symbolically. The command sequence would go something like this: ./gsu da0 m set bps=512 format (edit and write dos/bsd disk labels) q The FreeBSD port is still in a little bit of an "alpha" state. I can make it available on a "per request" basis. I ask only that the "alpha" versions not be redistributed. Dan Strick dan@math.berkeley.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 16 16:05:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10291 for freebsd-scsi-outgoing; Mon, 16 Nov 1998 16:05:49 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from n4hhe.ampr.org (tnt2-155.HiWAAY.net [208.147.148.155]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA10225 for ; Mon, 16 Nov 1998 16:05:41 -0800 (PST) (envelope-from dkelly@n4hhe.ampr.org) Received: from n4hhe.ampr.org (localhost.ampr.org [127.0.0.1]) by n4hhe.ampr.org (8.9.1/8.9.1) with ESMTP id SAA04617; Mon, 16 Nov 1998 18:04:41 -0600 (CST) (envelope-from dkelly@n4hhe.ampr.org) Message-Id: <199811170004.SAA04617@n4hhe.ampr.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Bernd Walter cc: freebsd-scsi@FreeBSD.ORG From: David Kelly Subject: Re: 520byte sector size In-reply-to: Message from Bernd Walter of "Mon, 16 Nov 1998 02:22:47 +0100." <19981116022247.23622@cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 16 Nov 1998 18:04:41 -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Bernd Walter writes: > da8 at ahc6 bus 0 target 3 lun 0 > da8: Fixed Direct Access SCSI2 device > da8: 5.0MB/s transfers (5.0MHz, offset 12) > da8: 388MB (782600 520 byte sectors: 64H 32S/T 382C) > > FreeBSD don't like this sector size very much :( > I know that they can be formated with 512 byte sectors. > I've done this with an old 1542 on a similar drive. > I just selected format in the BIOS-Tool and it lowlevel > formated it with 512 byte sectors. Recently I tried to resize the blocks on a 9G IBM drive that was StorageTek/Clariion OEM. No such luck. It was stuck at 520. Was using SGI's fx utility. The drive uses special firmware vs. over the counter units. Irix was happy to use the disk at 520 bytes/block. Problem was the drive didn't have a bad block list. And wouldn't let me manually add a bad block. But when put back into the RAID rack it came from it worked (still works a year later) perfectly. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 17 00:16:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA07621 for freebsd-scsi-outgoing; Tue, 17 Nov 1998 00:16:05 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dart.sr.se (dart.SR.SE [193.12.91.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA07615; Tue, 17 Nov 1998 00:16:03 -0800 (PST) (envelope-from gunnar@pluto.sr.se) Received: from honken.sr.se ([134.25.128.27]) by dart.sr.se (8.9.1/8.9.0) with ESMTP id JAA27976; Tue, 17 Nov 1998 09:15:23 +0100 (MET) Received: from pluto.sr.se (pluto.SR.SE [134.25.193.91]) by honken.sr.se (8.7.5/8.7.3) with ESMTP id JAA08929; Tue, 17 Nov 1998 09:15:22 +0100 (MET) Received: (from gunnar@localhost) by pluto.sr.se (8.8.8/8.8.8) id JAA29101; Tue, 17 Nov 1998 09:15:22 +0100 (CET) (envelope-from gunnar) Message-ID: <19981117091522.C28935@sr.se> Date: Tue, 17 Nov 1998 09:15:22 +0100 From: Gunnar Flygt To: lurkie@wxs.nl Cc: FreeBSD Questions , freebsd-scsi@FreeBSD.ORG Subject: Re: HP DAT tape loader Reply-To: flygt@sr.se References: <19981116152942.C27075@sr.se> <199811170840480616.23707C92@wwwintern.kleurbeeld.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.93.2i In-Reply-To: <199811170840480616.23707C92@wwwintern.kleurbeeld.nl>; from Marc Veldman on Tue, Nov 17, 1998 at 08:40:48AM +0100 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Nov 17, 1998 at 08:40:48AM +0100, Marc Veldman wrote: > Hi Gunnar, > > >Is it a ´dead end´ trying to connect a HP 1553 DAT loader to FreeBSD > >3.0? It's a '6 DAT-tapes in a packet´ backup unit. > > I'm not sure it's a dead end, but it sure is a maze. > I've connected it to my machine and it will run as a normal tape drive, > and you can load/unload the tapes in sequence. > mt offline will unload the current tape and load the next one. Maybe that is enough to make it work OK, together with amanda. > Getting chio to work depends on your SCSI adapter. > On a Future Domain 950 controller it will not work, > on an Adaptec 1542 it seems to work, but in the FreeBSD-scsi archives The controller is Adaptec 2940W. > I read something about a bit of broken code in the SCSI drivers, > but I can't remember where. > > Sorry for not giving you a definite yes or no, but I'm also a little lost here. > Maybe someone at FreeBSD-SCSI can help you. I'll x-post it to that list. Thanks! > > Have a nice day, It's snowing, but might be a nice day anyway :-) Same to you! -- __o regards, Gunnar ---_ \<,_ email: flygt@sr.se ---- (_)/ (_) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 17 03:53:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA28626 for freebsd-scsi-outgoing; Tue, 17 Nov 1998 03:53:37 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA28607 for ; Tue, 17 Nov 1998 03:53:13 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id MAA26212 for freebsd-scsi@FreeBSD.ORG; Tue, 17 Nov 1998 12:52:42 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id MAA15797; Tue, 17 Nov 1998 12:22:53 +0100 (MET) (envelope-from j) Message-ID: <19981117122253.18551@uriah.heep.sax.de> Date: Tue, 17 Nov 1998 12:22:53 +0100 From: J Wunsch To: freebsd-scsi@FreeBSD.ORG Subject: Re: 520byte sector size Reply-To: Joerg Wunsch References: <199811162152.NAA14263@math.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199811162152.NAA14263@math.berkeley.edu>; from Dan Strick on Mon, Nov 16, 1998 at 01:52:48PM -0800 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Dan Strick wrote: > I believe the correct method is to change the "data bytes per phys sector" > parameter (bytes 12 and 13, big endian) on the "format parameter page" > (page code 3) immediately before reformatting. That's not completely true. The SCSI standard isn't very specific in this, and a number of comments and notes that are located in the description of block descriptors imply that you can use them to alter the (logical) block size possibly requiring a future FORMAT UNIT command to get into effect. Physical sectors aren't necessarily the same as logical blocks, and you're only actually interested in logical blocks (this is what the READ and WRITE commands handle). So the outcome is, both ways (block size in the block descriptor, and physical sector size in the medium format page) cannot clearly be dismissed as ``not supported by the standard'' and are apparently allowed. > I have a program that lets you manually edit individual fields of > mode pages symbolically. The command sequence would go something > like this: Hmm, something like scsi -e -m (old SCSI system), or camcontrol -e -m (CAM system)? FreeBSD used to have it for years... -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 17 03:53:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA28639 for freebsd-scsi-outgoing; Tue, 17 Nov 1998 03:53:42 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA28634 for ; Tue, 17 Nov 1998 03:53:40 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id MAA26213 for freebsd-scsi@FreeBSD.ORG; Tue, 17 Nov 1998 12:53:12 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id MAA15806; Tue, 17 Nov 1998 12:23:42 +0100 (MET) (envelope-from j) Message-ID: <19981117122342.24968@uriah.heep.sax.de> Date: Tue, 17 Nov 1998 12:23:42 +0100 From: J Wunsch To: freebsd-scsi@FreeBSD.ORG Subject: Re: 520byte sector size Reply-To: Joerg Wunsch References: <19981116081950.08123@uriah.heep.sax.de> <199811160818.BAA26903@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199811160818.BAA26903@panzer.plutotech.com>; from Kenneth D. Merry on Mon, Nov 16, 1998 at 01:18:22AM -0700 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Kenneth D. Merry wrote: > There isn't an easy option to edit the mode page header, or block > descriptor from camcontrol. Btw., i've been confused, it's actually done by specifying the block size in the block descriptor (i originally wrote `mode page header', which is wrong). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 17 07:01:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA22010 for freebsd-scsi-outgoing; Tue, 17 Nov 1998 07:01:15 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from gauntlet2b.bridge.com (ns2.bridge.com [159.43.254.220]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA21990; Tue, 17 Nov 1998 07:01:11 -0800 (PST) (envelope-from mhughes@logroad.bridge.com) Received: by gauntlet2b.bridge.com; id JAA06964; Tue, 17 Nov 1998 09:00:33 -0600 (CST) Received: from dns1srv.bridge.com(167.76.56.13) by gauntlet2b.bridge.com via smap (4.1) id xma006313; Tue, 17 Nov 98 09:00:11 -0600 Received: from logroad.bridge.com (logroad.bridge.com [167.76.15.21]) by dns1srv.bridge.com (8.7.6/8.7.3) with SMTP id JAA01279; Tue, 17 Nov 1998 09:00:11 -0600 (CST) Received: by logroad.bridge.com (SMI-8.6/SMI-SVR4) id IAA28938; Tue, 17 Nov 1998 08:59:59 -0600 From: mhughes@logroad.bridge.com (Michael Hughes) Message-Id: <199811171459.IAA28938@logroad.bridge.com> Subject: Re: HP DAT tape loader To: flygt@sr.se Date: Tue, 17 Nov 1998 08:59:59 -0600 (CST) Cc: lurkie@wxs.nl, questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG In-Reply-To: <19981117091522.C28935@sr.se> from "Gunnar Flygt" at Nov 17, 98 09:15:22 am X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Gunnar Flygt said in email to me: > > On Tue, Nov 17, 1998 at 08:40:48AM +0100, Marc Veldman wrote: > > Hi Gunnar, > >=20 > > >Is it a =B4dead end=B4 trying to connect a HP 1553 DAT loader to FreeB= > SD > > >3.0? It's a '6 DAT-tapes in a packet=B4 backup unit. > >=20 > > I'm not sure it's a dead end, but it sure is a maze. > > I've connected it to my machine and it will run as a normal tape drive, > > and you can load/unload the tapes in sequence. > > mt offline will unload the current tape and load the next one. > > Maybe that is enough to make it work OK, together with amanda. > > > Getting chio to work depends on your SCSI adapter. > > On a Future Domain 950 controller it will not work, > > on an Adaptec 1542 it seems to work, but in the FreeBSD-scsi archives Take a look at PR 4270 and PR 6528, they have patches that fix the problems you are having with chio. > > The controller is Adaptec 2940W. > > > I read something about a bit of broken code in the SCSI drivers, > > but I can't remember where. > >=20 > > Sorry for not giving you a definite yes or no, but I'm also a little lo= > st here. > > Maybe someone at FreeBSD-SCSI can help you. > > I'll x-post it to that list. Thanks! > > >=20 > > Have a nice day, > > It's snowing, but might be a nice day anyway :-) Same to you! > > --=20 > __o > regards, Gunnar ---_ \<,_ > email: flygt@sr.se ---- (_)/ (_) > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > > -- ------------------------------------------------------------------------------- _ _ _ _ _ , Loghome living is the ' ) ) ) / // ' ) / / best ! / / / o _. /_ __. _ // /--/ . . _, /_ _ _ / ' (_<_(__/ /_(_/|_ Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA12776 for freebsd-scsi-outgoing; Tue, 17 Nov 1998 13:01:07 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA12765; Tue, 17 Nov 1998 13:01:04 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id OAA06277; Tue, 17 Nov 1998 14:00:21 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199811172100.OAA06277@panzer.plutotech.com> Subject: Re: HP DAT tape loader In-Reply-To: <19981117091522.C28935@sr.se> from Gunnar Flygt at "Nov 17, 98 09:15:22 am" To: flygt@sr.se Date: Tue, 17 Nov 1998 14:00:21 -0700 (MST) Cc: lurkie@wxs.nl, questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Gunnar Flygt wrote... > On Tue, Nov 17, 1998 at 08:40:48AM +0100, Marc Veldman wrote: > > Hi Gunnar, > > > > >Is it a ´dead end´ trying to connect a HP 1553 DAT loader to FreeBSD > > >3.0? It's a '6 DAT-tapes in a packet´ backup unit. > > > > I'm not sure it's a dead end, but it sure is a maze. > > I've connected it to my machine and it will run as a normal tape drive, > > and you can load/unload the tapes in sequence. > > mt offline will unload the current tape and load the next one. > > Maybe that is enough to make it work OK, together with amanda. > > > Getting chio to work depends on your SCSI adapter. > > On a Future Domain 950 controller it will not work, > > on an Adaptec 1542 it seems to work, but in the FreeBSD-scsi archives > > The controller is Adaptec 2940W. > > > I read something about a bit of broken code in the SCSI drivers, > > but I can't remember where. > > > > Sorry for not giving you a definite yes or no, but I'm also a little lost here. > > Maybe someone at FreeBSD-SCSI can help you. > > I'll x-post it to that list. Thanks! What exactly is the problem with the drive in question? If it's a problem in CAM, we'd like to fix it. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 17 13:53:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA21442 for freebsd-scsi-outgoing; Tue, 17 Nov 1998 13:53:17 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from vss.sci-nnov.ru (vss.sci-nnov.ru [193.125.71.26]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA21412 for ; Tue, 17 Nov 1998 13:53:02 -0800 (PST) (envelope-from dmiter@sci-nnov.ru) Received: from winhome (home.sci-nnov.ru [194.190.176.102]) by vss.sci-nnov.ru (8.8.8/Dmiter-4.2vss) with SMTP id AAA24949 for ; Wed, 18 Nov 1998 00:52:28 +0300 (MSK) Message-ID: <00e501be1274$62a7e830$0200000a@winhome.sci-nnov.ru> Reply-To: "Dmitry Eremin" From: "Dmitry Eremin" To: Subject: I need information. Date: Wed, 18 Nov 1998 00:51:07 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, Anybody can give me information haw write SCSI driver with CAM layer? Best regards. \|/ _________________________________________________________oOO_(o_o)_OOo___ Dmitry Eremin : dmiter@sci-nnov.ru : Fido: 2:5015/23 : N.Novgorod, Russia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 17 14:47:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02279 for freebsd-scsi-outgoing; Tue, 17 Nov 1998 14:47:14 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA02270 for ; Tue, 17 Nov 1998 14:47:12 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id PAA06868; Tue, 17 Nov 1998 15:46:34 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199811172246.PAA06868@panzer.plutotech.com> Subject: Re: I need information. In-Reply-To: <00e501be1274$62a7e830$0200000a@winhome.sci-nnov.ru> from Dmitry Eremin at "Nov 18, 98 00:51:07 am" To: dmiter@sci-nnov.ru Date: Tue, 17 Nov 1998 15:46:34 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (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 Dmitry Eremin wrote... > Hello, > > Anybody can give me information haw write SCSI driver with CAM layer? There isn't any documentation, other than the generic information here: http://www.freebsd.org/~gibbs The best thing to do is to look at some of the other CAM drivers for examples. (Matthew Jacob, Nicholas Souchu and Warner Losh have already written drivers that way, more or less. They all asked Justin questions, though, I think.) What kind of card do you want to write a driver for? It's possible someone else might be working on a driver already.. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 18 03:17:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA18835 for freebsd-scsi-outgoing; Wed, 18 Nov 1998 03:17:21 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from vss.sci-nnov.ru (vss.sci-nnov.ru [193.125.71.26]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA18808 for ; Wed, 18 Nov 1998 03:16:27 -0800 (PST) (envelope-from dmiter@sci-nnov.ru) Received: from winhome (home.sci-nnov.ru [194.190.176.102]) by vss.sci-nnov.ru (8.8.8/Dmiter-4.2vss) with SMTP id OAA07566; Wed, 18 Nov 1998 14:09:58 +0300 (MSK) Message-ID: <00a801be12e3$d6569ff0$0200000a@winhome.sci-nnov.ru> Reply-To: "Dmitry Eremin" From: "Dmitry Eremin" To: "Kenneth D. Merry" Cc: Subject: Re: I need information. Date: Wed, 18 Nov 1998 14:08:35 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >What kind of card do you want to write a driver for? It's possible someone >else might be working on a driver already.. I have the amd 53c974 scsi card. Shortly before this message I asked about this chip and as far as I understand nobody writes this driver. I say more. The old driver of this card had been removed from CVS tree some day ago. I don’t have possibility to buy a new card. I want to rewrite the old driver for a new CAM layer. Maybe someone help me? I don’t have enough experience to do this. I will glad to receive any information how do that. Best regards. \|/ _________________________________________________________oOO_(o_o)_OOo___ Dmitry Eremin : dmiter@sci-nnov.ru : Fido: 2:5015/23 : N.Novgorod, Russia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 18 15:27:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28682 for freebsd-scsi-outgoing; Wed, 18 Nov 1998 15:27:34 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from math.berkeley.edu (math.Berkeley.EDU [128.32.183.94]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA28669 for ; Wed, 18 Nov 1998 15:27:28 -0800 (PST) (envelope-from dan@math.berkeley.edu) Received: (from dan@localhost) by math.berkeley.edu (8.8.7/8.8.7) id PAA21734; Wed, 18 Nov 1998 15:26:51 -0800 (PST) Date: Wed, 18 Nov 1998 15:26:51 -0800 (PST) From: dan@math.berkeley.edu (Dan Strick) Message-Id: <199811182326.PAA21734@math.berkeley.edu> To: joerg_wunsch@uriah.heep.sax.de Subject: Re: 520byte sector size Cc: dan@math.berkeley.edu, freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I believe the correct method is to change the "data bytes per phys sector" > > parameter (bytes 12 and 13, big endian) on the "format parameter page" > > (page code 3) immediately before reformatting. > > That's not completely true. The SCSI standard isn't very specific in > this, and a number of comments and notes that are located in the > description of block descriptors imply that you can use them to alter > the (logical) block size possibly requiring a future FORMAT UNIT > command to get into effect. I stand corrected. I had not read the fine print in the SCSI standard(s) for several years and forgot. I just checked a couple of disk drives and discovered that these drives treat the "data bytes per phys sector" in the "format parameter page" to be unchangeable. For these drives you have to set the bock size via a mode select block descriptor. > > I have a program that lets you manually edit individual fields of > > mode pages symbolically. The command sequence would go something > > like this: > > Hmm, something like scsi -e -m (old SCSI system), or > camcontrol -e -m (CAM system)? I am not very familiar with the standard FreeBSD facility since I have never had to use it, but it does seem to provide an equivalent capability. Naturally, I unreasonably prefer the facility that I invented. > FreeBSD used to have it for years... If only I had known, I could have saved myself a lot of effort. Unfortunately, I only started using FreeBSD about three years ago. I wrote the first version of my SCSI utility about ten years ago. Such a waste ... Life is so depressing ... Dan Strick dan@math.berkeley.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 18 17:24:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17713 for freebsd-scsi-outgoing; Wed, 18 Nov 1998 17:24:35 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from digital.net (max-roc6-8.digital.net [208.14.38.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17700; Wed, 18 Nov 1998 17:24:19 -0800 (PST) (envelope-from kcw@digital.net) Received: (from kcw@localhost) by digital.net (8.8.8/8.8.8) id UAA00336; Wed, 18 Nov 1998 20:09:38 -0500 (EST) (envelope-from kcw) To: freebsd-scsi@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: scsi tape-drive and "extraneous data discarded, COMMAND FAILED" X-Face: O~Rn;(l][/-o1sALg4A@xpE:9-"'IR[%;,,!m7 Date: 18 Nov 1998 20:09:38 -0500 Message-ID: <8767cc8p4d.fsf@digital.net> Lines: 103 X-Mailer: Gnus v5.4.37/XEmacs 19.15 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi - I recently moved my internal Wangtek 5525 scsi tape drive from inside my computer case to an external scsi encloser. The Wangtek has been working just great the past couple of years inside my computer case and using FreeBSD. But now it is acting up with FreeBSD since I moved it to the external encloser. When the Wangtek was inside my case, it was the terminating device. It has the terminator packs in place on the unit. My CD-ROM drive is now terminating my internal bus, and the Wangtek is terminating the external bus (with its terminator packs). My scsi controller is a PCI Tyan S1365 with the NCR 875 chip. As you can see from the "dmesg" output below, FreeBSD is communicating with the Wangtek. However, not well enough to do dumps and restores. When the tape unit was internal to my case, I had no such error messages. I now have the Wangtek set for scsi id 4. Are there any kernel options or scsi parameters I can tweak to get this working ? Any ideas ? thanks - Ken Whedbee Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2.6-RELEASE #0: Mon Nov 16 20:11:25 EST 1998 kcw@bonkers:/usr/src/sys/compile/WEB_KERN CPU: Pentium (99.72-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x526 Stepping=6 Features=0x1bf real memory = 33554432 (32768K bytes) avail memory = 31084544 (30356K bytes) Probing for devices on PCI bus 0: chip0 rev 1 on pci0:0:0 chip1 rev 0 on pci0:7:0 chip2 rev 0 on pci0:7:1 vga0 rev 9 on pci0:17:0 ncr0 rev 3 int a irq 10 on pci0:19:0 (ncr0:0:0): "SEAGATE ST34520N 1335" type 0 fixed SCSI 2 sd0(ncr0:0:0): Direct-Access sd0(ncr0:0:0): 20.0 MB/s (50 ns, offset 15) 4345MB (8899737 512 byte sectors) (ncr0:1:0): "SEAGATE ST31200N 8648" type 0 fixed SCSI 2 sd1(ncr0:1:0): Direct-Access sd1(ncr0:1:0): 10.0 MB/s (100 ns, offset 15) 1006MB (2061108 512 byte sectors) (ncr0:2:0): "SEAGATE ST51080N 0958" type 0 fixed SCSI 2 sd2(ncr0:2:0): Direct-Access sd2(ncr0:2:0): 10.0 MB/s (100 ns, offset 15) 1030MB (2109840 512 byte sectors) (ncr0:3:0): "NEC CD-ROM DRIVE:463 1.05" type 5 removable SCSI 2 cd0(ncr0:3:0): CD-ROM cd0(ncr0:3:0): 10.0 MB/s (100 ns, offset 15) can't get the size (ncr0:4:0): extraneous data discarded. (ncr0:4:0): COMMAND FAILED (9 80) @f03e2800. (ncr0:4:0): extraneous data discarded. (ncr0:4:0): COMMAND FAILED (9 80) @f03e2800. (ncr0:4:0): extraneous data discarded. (ncr0:4:0): COMMAND FAILED (9 80) @f03e2800. (ncr0:4:0): "WANGTEK 5525ES SCSI REV1" type 1 removable SCSI 2 st0(ncr0:4:0): Sequential-Access st0(ncr0:4:0): asynchronous. density code 0x0, st0(ncr0:4:0): extraneous data discarded. st0(ncr0:4:0): COMMAND FAILED (9 80) @f058f000. st0(ncr0:4:0): extraneous data discarded. st0(ncr0:4:0): COMMAND FAILED (9 80) @f058f000. st0(ncr0:4:0): extraneous data discarded. st0(ncr0:4:0): COMMAND FAILED (9 80) @f058f000. drive empty pci0:20: vendor=0x1274, device=0x5000, class=multimedia (audio) int a irq 11 [no driver assigned] Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in aha0 not found at 0x330 npx0 on motherboard npx0: INT 16 interface changing root device to st1s1a Intel Pentium F00F detected, installing workaround To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 18 21:22:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA10893 for freebsd-scsi-outgoing; Wed, 18 Nov 1998 21:22:12 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA10884 for ; Wed, 18 Nov 1998 21:22:10 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id WAA24093; Wed, 18 Nov 1998 22:14:09 -0700 (MST) Date: Wed, 18 Nov 1998 22:14:09 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199811190514.WAA24093@narnia.plutotech.com> To: "Dmitry Eremin" cc: scsi@FreeBSD.ORG Subject: Re: I need information. X-Newsgroups: pluto.freebsd.scsi In-Reply-To: <00a801be12e3$d6569ff0$0200000a@winhome.sci-nnov.ru> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-BETA (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <00a801be12e3$d6569ff0$0200000a@winhome.sci-nnov.ru> you wrote: >>What kind of card do you want to write a driver for? It's possible someone >>else might be working on a driver already.. > > I have the amd 53c974 scsi card. Shortly before this message I asked about I'm working on getting one of these cards. If I can get one, I can probably whip up a driver in a few days. I can certainly answer any questions you have about CAM if you start working on a port. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 19 00:07:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA26149 for freebsd-scsi-outgoing; Thu, 19 Nov 1998 00:07:07 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from nordix.no (gw.nordix.no [195.18.177.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA26139 for ; Thu, 19 Nov 1998 00:07:01 -0800 (PST) (envelope-from bjorna@nordix.no) Received: from nordix.no (bjorna.nordix.no [195.18.179.124]) by nordix.no (8.8.7/8.8.7) with ESMTP id KAA01472 for ; Thu, 19 Nov 1998 10:35:13 +0100 Message-ID: <3653D15E.FA7A3A61@nordix.no> Date: Thu, 19 Nov 1998 09:05:50 +0100 From: "=?iso-8859-1?Q?Bj=F8rn?= M. H. Aune" Organization: NordiX Data AS X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: scsi@FreeBSD.ORG Subject: About the NCR 53C896 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi there! URGENT! We're working on a project with the Intel SC450NX Server... Is the onboard SCSI controller, NCR 53C896 supported by FreeBSD? Regards Bjorn Aune To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 19 00:54:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA01923 for freebsd-scsi-outgoing; Thu, 19 Nov 1998 00:54:57 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA01872 for ; Thu, 19 Nov 1998 00:54:51 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 28870 invoked by uid 1001); 19 Nov 1998 08:54:15 +0000 (GMT) To: bjorna@nordix.no Cc: scsi@FreeBSD.ORG Subject: Re: About the NCR 53C896 In-Reply-To: Your message of "Thu, 19 Nov 1998 09:05:50 +0100" References: <3653D15E.FA7A3A61@nordix.no> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Thu, 19 Nov 1998 09:54:14 +0100 Message-ID: <28863.911465654@verdi.nethelp.no> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > We're working on a project with the Intel SC450NX Server... > Is the onboard SCSI controller, NCR 53C896 supported by FreeBSD? Um, how about taking a look at the code? From sys/pci/ncr.c in FreeBSD-current: static ncr_chip ncr_chip_table[] = { ... {NCR_896_ID, 0x00, "ncr 53c896 fast40 wide scsi", 7, 31, 7, FE_WIDE|FE_ULTRA2|FE_QUAD|FE_CACHE_SET|FE_DFS|FE_LDSTR|FE_PFEN|FE_RAM} }; Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 19 07:59:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA12863 for freebsd-scsi-outgoing; Thu, 19 Nov 1998 07:59:18 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from farm.farm.sperry-sun.com ([32.97.92.188]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA12858 for ; Thu, 19 Nov 1998 07:59:16 -0800 (PST) (envelope-from rich@FreeBSD.org) Received: from rich.farm.sperry-sun.com (rich@rich.farm.sperry-sun.com [10.216.65.2]) by farm.farm.sperry-sun.com (8.9.1/8.9.1) with ESMTP id JAA27775 for ; Thu, 19 Nov 1998 09:58:47 -0600 (CST) (envelope-from rich@FreeBSD.org) Received: (from rich@localhost) by rich.farm.sperry-sun.com (8.9.1/8.9.1) id JAA08462; Thu, 19 Nov 1998 09:57:04 -0600 (CST) (envelope-from rich@rich.farm.sperry-sun.com) Date: Thu, 19 Nov 1998 09:57:04 -0600 (CST) Message-Id: <199811191557.JAA08462@rich.farm.sperry-sun.com> X-Authentication-Warning: rich.farm.sperry-sun.com: rich set sender to rich@rich.farm.sperry-sun.com using -f From: Murphey To: scsi@FreeBSD.ORG Subject: multi-tape backup? Reply-to: rich@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is there currently any way to backup a single filesystem (e.g. on a ccd array) across multiple tapes in a DAT autoloader? Thanks, Rich To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 19 11:16:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07978 for freebsd-scsi-outgoing; Thu, 19 Nov 1998 11:16:14 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from silver.gn.iaf.nl (silver.gn.iaf.nl [193.67.144.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07973; Thu, 19 Nov 1998 11:16:12 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by silver.gn.iaf.nl (8.8.8/8.8.8) with SMTP id UAA11079; Thu, 19 Nov 1998 20:15:41 +0100 Received: by uni4nn.gn.iaf.nl with UUCP id AA17208 (5.67b/IDA-1.5); Thu, 19 Nov 1998 20:11:49 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id TAA00615; Thu, 19 Nov 1998 19:23:15 +0100 (CET) From: Wilko Bulte Message-Id: <199811191823.TAA00615@yedi.iaf.nl> Subject: Re: scsi tape-drive and "extraneous data discarded, COMMAND FAILED" In-Reply-To: <8767cc8p4d.fsf@digital.net> from Ken Whedbee at "Nov 18, 98 08:09:38 pm" To: whedbee@digital.net (Ken Whedbee) Date: Thu, 19 Nov 1998 19:23:15 +0100 (CET) Cc: freebsd-scsi@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (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 As Ken Whedbee wrote... > Hi - > > I recently moved my internal Wangtek 5525 scsi tape drive from inside my > computer case to an external scsi encloser. The Wangtek has been working > just great the past couple of years inside my computer case and using > FreeBSD. But now it is acting up with FreeBSD since I moved it to the > external encloser. > > When the Wangtek was inside my case, it was the terminating device. It > has the terminator packs in place on the unit. My CD-ROM drive is now > terminating my internal bus, and the Wangtek is terminating the external > bus (with its terminator packs). My scsi controller is a PCI Tyan S1365 > with the NCR 875 chip. > > As you can see from the "dmesg" output below, FreeBSD is communicating > with the Wangtek. However, not well enough to do dumps and restores. > When the tape unit was internal to my case, I had no such error messages. > I now have the Wangtek set for scsi id 4. How long is your SCSI cable/bus now? As you are running Fast-20 aka Ultra SCSI you better keep it below 1.5 maybe 2 meters. In addition, using two different cable types, flatcable internally, round outside (I guess) are not the best thing to do. You might also consider using external active terminators instead of the resistor packs of the devices themselves. Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 19 11:51:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12370 for freebsd-scsi-outgoing; Thu, 19 Nov 1998 11:51:58 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA12357 for ; Thu, 19 Nov 1998 11:51:56 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id UAA07608; Thu, 19 Nov 1998 20:50:58 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id UAA24058; Thu, 19 Nov 1998 20:40:49 +0100 (MET) (envelope-from j) Message-ID: <19981119204048.20611@uriah.heep.sax.de> Date: Thu, 19 Nov 1998 20:40:48 +0100 From: J Wunsch To: Ken Whedbee Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: scsi tape-drive and "extraneous data discarded, COMMAND FAILED" Reply-To: Joerg Wunsch References: <8767cc8p4d.fsf@digital.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <8767cc8p4d.fsf@digital.net>; from Ken Whedbee on Wed, Nov 18, 1998 at 08:09:38PM -0500 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Ken Whedbee wrote: > As you can see from the "dmesg" output below, FreeBSD is communicating > with the Wangtek. However, not well enough to do dumps and restores. > When the tape unit was internal to my case, I had no such error messages. > I now have the Wangtek set for scsi id 4. Probably your bus got too long. With that many devices and the attempt to run it with 20 MHz (for sd0), you're only allowed to have 1.5 m of cabling (in total). Perhaps you'd better spend a second controller for the external bus? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 19 11:53:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12633 for freebsd-scsi-outgoing; Thu, 19 Nov 1998 11:53:14 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA12456; Thu, 19 Nov 1998 11:52:08 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id UAA07622; Thu, 19 Nov 1998 20:51:31 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id UAA24072; Thu, 19 Nov 1998 20:42:18 +0100 (MET) (envelope-from j) Message-ID: <19981119204218.52989@uriah.heep.sax.de> Date: Thu, 19 Nov 1998 20:42:18 +0100 From: J Wunsch To: rich@FreeBSD.ORG Cc: scsi@FreeBSD.ORG Subject: Re: multi-tape backup? Reply-To: Joerg Wunsch References: <199811191557.JAA08462@rich.farm.sperry-sun.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199811191557.JAA08462@rich.farm.sperry-sun.com>; from Murphey on Thu, Nov 19, 1998 at 09:57:04AM -0600 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Murphey wrote: > Is there currently any way to backup a single > filesystem (e.g. on a ccd array) across multiple tapes > in a DAT autoloader? dump(8) can handle multiple tapes, but i'm afraid it won't talk to chio(8). Perhaps you're going to teach it this? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 19 13:29:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20575 for freebsd-scsi-outgoing; Thu, 19 Nov 1998 13:29:47 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from maui.net (maui.net [207.175.210.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20568 for ; Thu, 19 Nov 1998 13:29:45 -0800 (PST) (envelope-from langfod@kauai.pacificglobal.net) Received: from kauai.pacificglobal.net (Kauai.PacificGlobal.NET [209.84.182.101]) by maui.net (8.8.7/8.8.5) with ESMTP id LAA19300 for ; Thu, 19 Nov 1998 11:29:13 -1000 (HST) Received: (from langfod@localhost) by kauai.pacificglobal.net (8.8.8/8.8.5) id LAA28339 for scsi@freebsd.org; Thu, 19 Nov 1998 11:29:07 -1000 (HST) From: David Langford Message-Id: <199811192129.LAA28339@kauai.pacificglobal.net> Subject: Newfs errors... To: scsi@FreeBSD.ORG Date: Thu, 19 Nov 1998 11:29:06 -1000 (HST) X-blank-line: This space intentionaly left blank. X-Mailer: ELM [version 2.4ME+ PL43 (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 While trying to newfs a ccd partition newfs gives me: newfs: ioctl (WDINFO): No such process newfs: /dev/rccd0c: can't rewrite disk label What may be going wrong? Thanks, -David Langford langfod@dihelix.com #newfs /dev/rccd0c Warning: 4048 sector(s) in last cylinder unallocated /dev/rccd0c: 34377776 sectors in 8394 cylinders of 1 tracks, 4096 sectors 16786.0MB in 525 cyl groups (16 c/g, 32.00MB/g, 7936 i/g) super-block backups (for fsck -b #) at: 32, 65568, ... ... 34013216, 34078752, 34144288, 34209824, 34275360, 34340896, newfs: ioctl (WDINFO): No such process newfs: /dev/rccd0c: can't rewrite disk label # uname -a FreeBSD XXX 3.0-CURRENT FreeBSD 3.0-CURRENT #0: Mon Nov 9 18:09:13 HST 1998 root@XXX:/usr/src/sys/compile/XXX i386 # ccdconfig -g ccd0 16 0 /dev/da1c /dev/da2c /dev/da3c /dev/da4c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 19 15:16:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05619 for freebsd-scsi-outgoing; Thu, 19 Nov 1998 15:16:32 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from silver.gn.iaf.nl (silver.gn.iaf.nl [193.67.144.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05612; Thu, 19 Nov 1998 15:16:26 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by silver.gn.iaf.nl (8.8.8/8.8.8) with SMTP id AAA20450; Fri, 20 Nov 1998 00:15:55 +0100 Received: by uni4nn.gn.iaf.nl with UUCP id AA28246 (5.67b/IDA-1.5); Thu, 19 Nov 1998 23:51:32 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id XAA03478; Thu, 19 Nov 1998 23:40:20 +0100 (CET) From: Wilko Bulte Message-Id: <199811192240.XAA03478@yedi.iaf.nl> Subject: Re: multi-tape backup? In-Reply-To: <19981119204218.52989@uriah.heep.sax.de> from J Wunsch at "Nov 19, 98 08:42:18 pm" To: joerg_wunsch@uriah.heep.sax.de Date: Thu, 19 Nov 1998 23:40:20 +0100 (CET) Cc: rich@FreeBSD.ORG, scsi@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (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 As J Wunsch wrote... > As Murphey wrote: > > > Is there currently any way to backup a single > > filesystem (e.g. on a ccd array) across multiple tapes > > in a DAT autoloader? > > dump(8) can handle multiple tapes, but i'm afraid it won't talk to > chio(8). Perhaps you're going to teach it this? Some loaders can be set to 'sequential mode' which in this case means if they hit EOT they rewind the current tape and load a new one into the drive. I know for example that DLT loaders can be set up to do so. Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 20 14:31:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28649 for freebsd-scsi-outgoing; Fri, 20 Nov 1998 14:31:09 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from house.key.net.au (house.key.net.au [203.35.4.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28639 for ; Fri, 20 Nov 1998 14:31:03 -0800 (PST) (envelope-from keith@apcs.com.au) Received: (from uucp@localhost) by house.key.net.au (8.8.8/8.8.8) id JAA08489; Sat, 21 Nov 1998 09:30:19 +1100 (EST) (envelope-from keith@apcs.com.au) Received: from well.apcs.com.au(203.35.4.19) via SMTP by mailgw.key.net.au, id smtpdif8487; Sat Nov 21 09:30:09 1998 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 In-Reply-To: <199811202220.MAA07661@kauai.pacificglobal.net> Date: Sat, 21 Nov 1998 09:31:44 +1100 (EST) Reply-To: keith@apcs.com.au Organization: Australia Power Control Systems P/L From: Keith Anderson To: David Langford Subject: RE: Newfs errors... Cc: scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi David You cant label this disk because its not a real drive. follow the instructions on http://www.freebsd.org/tutorials/diskformat/diskformat.html down about 3/4 of the page is good info on ccd and it worked fine for me look in the FAQ some good info there ! Keith On 19-Nov-98 David Langford wrote: > While trying to newfs a ccd partition newfs gives me: > > newfs: ioctl (WDINFO): No such process > newfs: /dev/rccd0c: can't rewrite disk label > > What may be going wrong? > Thanks, > -David Langford > langfod@dihelix.com > > >#newfs /dev/rccd0c > Warning: 4048 sector(s) in last cylinder unallocated > /dev/rccd0c: 34377776 sectors in 8394 cylinders of 1 tracks, 4096 sectors > 16786.0MB in 525 cyl groups (16 c/g, 32.00MB/g, 7936 i/g) > super-block backups (for fsck -b #) at: > 32, 65568, ... > ... > 34013216, 34078752, 34144288, 34209824, 34275360, 34340896, > newfs: ioctl (WDINFO): No such process > newfs: /dev/rccd0c: can't rewrite disk label > ># uname -a > FreeBSD XXX 3.0-CURRENT FreeBSD 3.0-CURRENT #0: Mon Nov 9 18:09:13 HST 1998 > root@XXX:/usr/src/sys/compile/XXX i386 > ># ccdconfig -g > ccd0 16 0 /dev/da1c /dev/da2c /dev/da3c /dev/da4c > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message --- ---------------------------------- E-Mail: Keith Anderson Date: 21-Nov-98 Time: 09:26:57 Satelite Service 64K to 2Meg This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 20 14:35:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29190 for freebsd-scsi-outgoing; Fri, 20 Nov 1998 14:35:19 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from maui.net (maui.net [207.175.210.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29183 for ; Fri, 20 Nov 1998 14:35:18 -0800 (PST) (envelope-from langfod@kauai.pacificglobal.net) Received: from kauai.pacificglobal.net (Kauai.PacificGlobal.NET [209.84.182.101]) by maui.net (8.8.7/8.8.5) with ESMTP id MAA16159; Fri, 20 Nov 1998 12:34:48 -1000 (HST) Received: (from langfod@localhost) by kauai.pacificglobal.net (8.8.8/8.8.5) id MAA08773; Fri, 20 Nov 1998 12:34:45 -1000 (HST) From: David Langford Message-Id: <199811202234.MAA08773@kauai.pacificglobal.net> Subject: Re: Newfs errors... In-Reply-To: from Keith Anderson at "Nov 21, 1998 9:31:44 am" To: keith@apcs.com.au Date: Fri, 20 Nov 1998 12:34:45 -1000 (HST) Cc: langfod@maui.net, scsi@FreeBSD.ORG X-blank-line: This space intentionaly left blank. X-Mailer: ELM [version 2.4ME+ PL43 (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 Huh? Who is trying to label. I use ccd all the time on other machines. This is the first 3.0-CURRENT/ELF box I have tried doing this on and "NEWFS" gives the error I outlined below. -David >You cant label this disk because its not a real drive. > >follow the instructions on >http://www.freebsd.org/tutorials/diskformat/diskformat.html > >down about 3/4 of the page is good info on ccd >and it worked fine for me >look in the FAQ some good info there ! > >Keith > >On 19-Nov-98 David Langford wrote: >> While trying to newfs a ccd partition newfs gives me: >> >> newfs: ioctl (WDINFO): No such process >> newfs: /dev/rccd0c: can't rewrite disk label >> >> What may be going wrong? >> Thanks, >> -David Langford >> langfod@dihelix.com >> >> >>#newfs /dev/rccd0c >> Warning: 4048 sector(s) in last cylinder unallocated >> /dev/rccd0c: 34377776 sectors in 8394 cylinders of 1 tracks, 4096 sectors >> 16786.0MB in 525 cyl groups (16 c/g, 32.00MB/g, 7936 i/g) >> super-block backups (for fsck -b #) at: >> 32, 65568, ... >> ... >> 34013216, 34078752, 34144288, 34209824, 34275360, 34340896, >> newfs: ioctl (WDINFO): No such process >> newfs: /dev/rccd0c: can't rewrite disk label >> >># uname -a >> FreeBSD XXX 3.0-CURRENT FreeBSD 3.0-CURRENT #0: Mon Nov 9 18:09:13 HST 1998 >> root@XXX:/usr/src/sys/compile/XXX i386 >> >># ccdconfig -g >> ccd0 16 0 /dev/da1c /dev/da2c /dev/da3c /dev/da4c >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-questions" in the body of the message > >--- >---------------------------------- >E-Mail: Keith Anderson >Date: 21-Nov-98 >Time: 09:26:57 >Satelite Service 64K to 2Meg >This message was sent by XFMail >---------------------------------- > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 20 14:43:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00496 for freebsd-scsi-outgoing; Fri, 20 Nov 1998 14:43:42 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from rain.futuresouth.com (rain.futuresouth.com [198.79.79.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00215 for ; Fri, 20 Nov 1998 14:42:53 -0800 (PST) (envelope-from stormy@rain.futuresouth.com) Received: (from stormy@localhost) by rain.futuresouth.com (8.9.1/8.9.1) id QAA14671 for scsi@FreeBSD.ORG; Thu, 19 Nov 1998 16:42:37 -0600 (CST) (envelope-from stormy) Message-ID: <19981119164237.A14667@futuresouth.com> Date: Thu, 19 Nov 1998 16:42:37 -0600 From: Stormy Henderson To: scsi@FreeBSD.ORG Subject: Re: Newfs errors... Mail-Followup-To: scsi@FreeBSD.ORG References: <199811202220.MAA07661@kauai.pacificglobal.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811202220.MAA07661@kauai.pacificglobal.net>; from David Langford on Thu, Nov 19, 1998 at 11:29:06AM -1000 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org A happy camper (David Langford, langfod@maui.net) once wrote... > While trying to newfs a ccd partition newfs gives me: > newfs: ioctl (WDINFO): No such process > newfs: /dev/rccd0c: can't rewrite disk label I think it does that for everyone. It did for me, and CCD nevertheless works fine. Be happy... -- http://www.futuresouth.com/~stormy/signature.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 20 20:12:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA05843 for freebsd-scsi-outgoing; Fri, 20 Nov 1998 20:12:52 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA05838 for ; Fri, 20 Nov 1998 20:12:50 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id UAA24934; Fri, 20 Nov 1998 20:12:14 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Fri, 20 Nov 1998 20:12:13 -0800 (PST) From: Doug White To: David Langford cc: scsi@FreeBSD.ORG Subject: Re: Newfs errors... In-Reply-To: <199811202220.MAA07661@kauai.pacificglobal.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 19 Nov 1998, David Langford wrote: > While trying to newfs a ccd partition newfs gives me: > > newfs: ioctl (WDINFO): No such process > newfs: /dev/rccd0c: can't rewrite disk label What version of FreeBSD? > > What may be going wrong? > Thanks, > -David Langford > langfod@dihelix.com > > > #newfs /dev/rccd0c > Warning: 4048 sector(s) in last cylinder unallocated > /dev/rccd0c: 34377776 sectors in 8394 cylinders of 1 tracks, 4096 sectors > 16786.0MB in 525 cyl groups (16 c/g, 32.00MB/g, 7936 i/g) > super-block backups (for fsck -b #) at: > 32, 65568, ... > ... > 34013216, 34078752, 34144288, 34209824, 34275360, 34340896, > newfs: ioctl (WDINFO): No such process > newfs: /dev/rccd0c: can't rewrite disk label > > # uname -a > FreeBSD XXX 3.0-CURRENT FreeBSD 3.0-CURRENT #0: Mon Nov 9 18:09:13 HST 1998 root@XXX:/usr/src/sys/compile/XXX i386 Hm, we had problems with newfs dying with 'no such device' (EXDEV), but not ESRCH. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message