From owner-freebsd-scsi Sun Apr 5 15:52:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09665 for freebsd-scsi-outgoing; Sun, 5 Apr 1998 15:52:30 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09660; Sun, 5 Apr 1998 15:52:26 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.8) with SMTP id PAA17724; Sun, 5 Apr 1998 15:52:24 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Date: Sun, 5 Apr 1998 15:52:23 -0700 (PDT) From: Doug White Reply-To: Doug White To: Malte Lance cc: questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: jumper-setting for SONY SDT-7000 In-Reply-To: <3.0.32.19980404133529.00749da0@cyclone.degnet.baynet.de> 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 Sat, 4 Apr 1998, Malte Lance wrote: > Does anyone have detailed info on the meaning of the > jumpers "DC Disable" and "Terminator Power" for the > SONY SDT-7000 ? Hm. >From the Sony web page http://www.ita.sel.sony.com/support/storage/faqs/dat.html#1: How does one set the SCSI ID, termination, term power, or parity on the SDT-5000/5200 tape drive? Please refer to the SDT-5000/5200 Jumper Setting document. A FAX copy of the SDT- 5000/5200 Jumper Settings document can be obtained by calling the Sony FAX Retrieval System at 1-800-883-7669, document 5761. That might explain `DC Disable'. I'm tempted to think `Data Compression Disable'. `Terminator Power' selects the source of terminator power; it should be set to come from the SCSI Bus. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Apr 6 00:13:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA13124 for freebsd-scsi-outgoing; Mon, 6 Apr 1998 00:13:16 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA13102; Mon, 6 Apr 1998 00:13:01 -0700 (PDT) (envelope-from semen@iclub.nsu.ru) Received: from localhost (semen@localhost) by iclub.nsu.ru (8.8.8/8.8.5) with SMTP id OAA05707; Mon, 6 Apr 1998 14:12:57 +0700 (NSS) Date: Mon, 6 Apr 1998 14:12:56 +0700 (NSS) From: Ustimenko Semen To: Doug White cc: Malte Lance , questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: jumper-setting for SONY SDT-7000 In-Reply-To: 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 Sun, 5 Apr 1998, Doug White wrote: > On Sat, 4 Apr 1998, Malte Lance wrote: > > > Does anyone have detailed info on the meaning of the > > jumpers "DC Disable" and "Terminator Power" for the > > SONY SDT-7000 ? > > ... > > That might explain `DC Disable'. I'm tempted to think `Data Compression > Disable'. `Terminator Power' selects the source of terminator power; it > should be set to come from the SCSI Bus. > As i've discovered on SDT-7000 Data Compression can not be controlled by software, and it is enabled unless you disable it by jumper. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Apr 6 02:50:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA29652 for freebsd-scsi-outgoing; Mon, 6 Apr 1998 02:50:28 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from cyclone.degnet.baynet.de (www.degnet.baynet.de [194.95.214.129]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA29635; Mon, 6 Apr 1998 02:50:23 -0700 (PDT) (envelope-from malte@webmore.com) Received: from bachus (unverified [194.95.214.188]) by cyclone.degnet.baynet.de (EMWAC SMTPRS 0.83) with SMTP id ; Mon, 06 Apr 1998 11:47:52 +0200 Message-Id: <3.0.32.19980406113752.006d6670@cyclone.degnet.baynet.de> X-Sender: moos@cyclone.degnet.baynet.de X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Mon, 06 Apr 1998 11:37:53 +0000 To: Doug White From: Malte Lance Subject: Re: jumper-setting for SONY SDT-7000 Cc: questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 15:52 05.04.98 -0700, you wrote: >On Sat, 4 Apr 1998, Malte Lance wrote: >> Does anyone have detailed info on the meaning of the >> jumpers "DC Disable" and "Terminator Power" for the >> SONY SDT-7000 ? >Hm. >From the Sony web page >http://www.ita.sel.sony.com/support/storage/faqs/dat.html#1: > How does one set the SCSI ID, termination, > term power, or parity on the SDT-5000/5200 > tape drive? > > Please refer to the SDT-5000/5200 Jumper > Setting document. A FAX copy of the SDT- > 5000/5200 Jumper Settings document can be > obtained by calling the Sony FAX Retrieval System > at 1-800-883-7669, document 5761. Nice service when you can call it. It is not possible from germany. :( The german Sony-center is too ignorant to provide that kind of service/ support. 2 x :( >That might explain `DC Disable'. I'm tempted to think `Data Compression >Disable'. Me too, but then why is it listed under the category "Terminators" ??? >`Terminator Power' selects the source of terminator power; it >should be set to come from the SCSI Bus. The labels for open/close-position of this jumper are "provided" and "Not provided". What should i choose ? (Ok ok ... answer it anyway please, since i want to be sure, other people understand it the same way i do). Why should it be set to "come from the SCSI Bus" ??? Why not set it to "get power for active termination on its own and not supply it to the SCSI Bus" ? Thanks for your help. Malte Lance malte@webmore.com > >Doug White | University of Oregon >Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant >http://gladstone.uoregon.edu/~dwhite | Computer Science Major > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Apr 6 03:58:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA05174 for freebsd-scsi-outgoing; Mon, 6 Apr 1998 03:58:57 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA05169 for ; Mon, 6 Apr 1998 03:58:55 -0700 (PDT) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.8.8/8.8.8) id LAA12724; Mon, 6 Apr 1998 11:58:50 +0100 (BST) (envelope-from joe) Message-ID: <19980406115850.43693@pavilion.net> Date: Mon, 6 Apr 1998 11:58:50 +0100 From: Josef Karthauser To: scsi@FreeBSD.ORG Subject: soft updates :( (no time) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i X-NCC-RegID: uk.pavilion Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does anyone know why I can't get softupdates to work? :( I've running a recently cvsup'd current, and have already 'make && make install'd the system. cc -c -O -m486 -pipe -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnes ted-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline - Wuninitialized -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h ../../ufs/ffs/ffs_softdep.c ../../ufs/ffs/ffs_softdep.c: In function `softdep_fsync': ../../ufs/ffs/ffs_softdep.c:3573: `time' undeclared (first use this function) ../../ufs/ffs/ffs_softdep.c:3573: (Each undeclared identifier is reported only o nce ../../ufs/ffs/ffs_softdep.c:3573: for each function it appears in.) ../../ufs/ffs/ffs_softdep.c: In function `flush_pagedep_deps': ../../ufs/ffs/ffs_softdep.c:3934: `time' undeclared (first use this function) *** Error code 1 Joe -- Josef Karthauser Technical Manager FreeBSD: The power to serve (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Apr 6 04:13:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA08968 for freebsd-scsi-outgoing; Mon, 6 Apr 1998 04:13:25 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from org.chem.msu.su (org.chem.msu.su [158.250.32.94]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA08444; Mon, 6 Apr 1998 04:11:42 -0700 (PDT) (envelope-from genie@qsar.chem.msu.su) Received: from org-qsar2.chem.msu.su (org-qsar2.chem.msu.su [158.250.48.99]) by org.chem.msu.su (8.8.7/8.8.5) with SMTP id PAA16109; Mon, 6 Apr 1998 15:03:38 +0400 (MSD) Message-ID: <005f01bd614b$b01d65c0$6330fa9e@org-qsar2.chem.msu.su> From: "Eugene Radchenko" To: "Alex" , Cc: , Subject: Re: SCSI errors with latest -current Date: Mon, 6 Apr 1998 15:03:38 +0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi! -----Original Message----- From: Alex Date: Sunday, April 05, 1998 12:43 AM Subject: Re: SCSI errors with latest -current On Sat, 4 Apr 1998, Andrey Chernov wrote: > With latest -current I start to get this sort of errors for my several > SCSI drives. Since they started at once for several drives, I suppose it > is not hardware problem. Any ideas? I find that if your disk system is pushed hard enough, that you will get errors like that with SCB paging and/or TAGGED_QUEUING enabled even before PHKs commits. This is one of the things the CAM code (dunno if it's stable enough to use) fixes. In essence it's a combination hardware and software problem... I think. As I tried to shout all over the SCSI list recently (to no avail), this is not limited to -current or 2.2.5. I had something like this even in 2.1 (though not as drastic -- just dump died and not the whole system). I have the feeling that 2.1 had not done tagged queueing yet. I hope now that one of the core team was bitten, this problem will be solved sooner ;-) BTW this definitely would classify as bug fix and as such, should be put in -stable, yes? I think many people are somewhat disappointed to obtain a release CD just to begin patching the system right after installation... Cheers Genie --- ######################################################### Eugene V. Radchenko Research associate, Computer Chemistry E-mail: genie@qsar.chem.msu.su http://org.chem.msu.su/~genie =================================================== "There are now new criminals out there that don't have guns. They have computers and many have other weapons of mass destruction." -- Janet Reno, Attorney General of the United States To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Apr 6 05:11:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA15422 for freebsd-scsi-outgoing; Mon, 6 Apr 1998 05:11:54 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA15401; Mon, 6 Apr 1998 05:11:50 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id FAA04001; Mon, 6 Apr 1998 05:04:03 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: "Eugene Radchenko" cc: "Alex" , ache@nagual.pp.ru, scsi@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: SCSI errors with latest -current In-reply-to: Your message of "Mon, 06 Apr 1998 15:03:38 +0400." <005f01bd614b$b01d65c0$6330fa9e@org-qsar2.chem.msu.su> Date: Mon, 06 Apr 1998 05:04:03 -0700 Message-ID: <3997.891864243@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > As I tried to shout all over the SCSI list recently (to no avail), this is > not limited to -current or 2.2.5. I had something like this even in 2.1 > (though not as drastic -- just dump died and not the whole system). I have > the feeling that 2.1 had not done tagged queueing yet. Things don't get fixed by shouting, they get fixed by fixing. That's free software. Feel free, Eugene! ;-) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Apr 6 09:44:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14502 for freebsd-scsi-outgoing; Mon, 6 Apr 1998 09:44:00 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from org.chem.msu.su (org.chem.msu.su [158.250.32.94]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14346; Mon, 6 Apr 1998 09:41:50 -0700 (PDT) (envelope-from genie@qsar.chem.msu.su) Received: from org-qsar2 (org-qsar2.chem.msu.su [158.250.48.99]) by org.chem.msu.su (8.8.7/8.8.5) with SMTP id UAA16807; Mon, 6 Apr 1998 20:19:37 +0400 (MSD) Message-ID: <002001bd6177$dc5c9760$6330fa9e@org-qsar2.chem.msu.su> From: "Eugene Radchenko" To: "Jordan K. Hubbard" Cc: "Alex" , , , Subject: Re: SCSI errors with latest -current Date: Mon, 6 Apr 1998 20:19:35 +0400 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.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Jordan, Don't (and did not) mean any flame, but if you had read my messages, you would know that they were not about 'Hey do fix this yesterday!'. I just asked someone (you know, not every user of the system has the expertise and time and a free machine to be SCSI hacker) to at least explain what this error means and what (in general terms) might be causing it and are there any ways to overcome this. The list archive search shows that this problem pops up every now and then, but I have seen no positive analysis except 'it should have been fixed in the previous version already'. I was disappointed not by the not-fixing of the problem (though I would appreciate seeing it fixed as the server dying in the middle of the night during backup is not a pleasant view for sysadmin). What gave me the unpleasant surprise was the complete indifference of readers (quite unusual for the FreeBSD _community_). Yours Genie -----Original Message----- From: Jordan K. Hubbard To: Eugene Radchenko Cc: Alex ; ache@nagual.pp.ru ; scsi@FreeBSD.ORG ; current@FreeBSD.ORG Date: Monday, April 06, 1998 4:05 PM Subject: Re: SCSI errors with latest -current >> As I tried to shout all over the SCSI list recently (to no avail), this is >> not limited to -current or 2.2.5. I had something like this even in 2.1 >> (though not as drastic -- just dump died and not the whole system). I have >> the feeling that 2.1 had not done tagged queueing yet. > >Things don't get fixed by shouting, they get fixed by fixing. That's >free software. Feel free, Eugene! ;-) > > Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Apr 6 13:18:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA29538 for freebsd-scsi-outgoing; Mon, 6 Apr 1998 13:18:55 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA29391; Mon, 6 Apr 1998 13:18:28 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.8) with SMTP id NAA19040; Mon, 6 Apr 1998 13:17:59 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Date: Mon, 6 Apr 1998 13:17:59 -0700 (PDT) From: Doug White Reply-To: Doug White To: Malte Lance cc: questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: jumper-setting for SONY SDT-7000 In-Reply-To: <3.0.32.19980406113752.006d6670@cyclone.degnet.baynet.de> 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 Mon, 6 Apr 1998, Malte Lance wrote: > Nice service when you can call it. It is not possible from germany. :( > The german Sony-center is too ignorant to provide that kind of service/ > support. 2 x :( How nice. > >`Terminator Power' selects the source of terminator power; it > >should be set to come from the SCSI Bus. > > The labels for open/close-position of this jumper are "provided" and > "Not provided". What should i choose ? (Ok ok ... answer it anyway please, > since i want to be sure, other people understand it the same way i do). > Why should it be set to "come from the SCSI Bus" ??? > Why not set it to "get power for active termination on its own and not > supply it to the SCSI Bus" ? Set to `not provided'. Provided probably means to provide power to the bus, which you don't want. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Apr 6 14:33:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16838 for freebsd-scsi-outgoing; Mon, 6 Apr 1998 14:33:29 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA16784 for ; Mon, 6 Apr 1998 14:33:14 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id XAA04553 for scsi@FreeBSD.ORG; Mon, 6 Apr 1998 23:32:51 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.9.0.Beta4/keltia-2.14/nospam) id VAA16444; Mon, 6 Apr 1998 21:28:47 +0200 (CEST) (envelope-from roberto) Message-ID: <19980406212847.A16435@keltia.freenix.fr> Date: Mon, 6 Apr 1998 21:28:47 +0200 From: Ollivier Robert To: scsi@FreeBSD.ORG Subject: Re: soft updates :( (no time) Mail-Followup-To: scsi@FreeBSD.ORG References: <19980406115850.43693@pavilion.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.4i In-Reply-To: <19980406115850.43693@pavilion.net>; from Josef Karthauser on Mon, Apr 06, 1998 at 11:58:50AM +0100 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4180 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to Josef Karthauser: > Does anyone know why I can't get softupdates to work? :( Because you didn't read freebsd-current and didn't see the discussion about "time"... :-) The first hunk fixes a panic. --- ffs_softdep.c.orig Fri Feb 20 21:12:51 1998 +++ ffs_softdep.c Wed Apr 1 00:50:13 1998 @@ -1528,6 +1528,14 @@ newindirdep->ir_state = ATTACHED; LIST_INIT(&newindirdep->ir_deplisthd); LIST_INIT(&newindirdep->ir_donehd); + if (bp->b_blkno == bp->b_lblkno) { +#ifdef DEBUG + printf("setup_allocindir_phase2: need bmap, blk %d\n", + bp->b_lblkno); +#endif + VOP_BMAP(bp->b_vp, bp->b_lblkno, NULL, &bp->b_blkno, + NULL, NULL); + } newindirdep->ir_saveddata = (ufs_daddr_t *)bp->b_data; newindirdep->ir_savebp = getblk(ip->i_devvp, bp->b_blkno, bp->b_bcount, 0, 0); @@ -3570,7 +3578,7 @@ } vn_lock(vp, LK_EXCLUSIVE | LK_RETRY, p); if (flushparent) { - tv = time; + getmicrotime(&tv); if (error = UFS_UPDATE(pvp, &tv, &tv, MNT_WAIT)) { vput(pvp); return (error); @@ -3931,7 +3939,7 @@ * has a MKDIR_PARENT dependency. */ if (dap->da_state & MKDIR_PARENT) { - tv = time; + getmicrotime(&tv); FREE_LOCK(&lk); if (error = UFS_UPDATE(pvp, &tv, &tv, MNT_WAIT)) break; @@ -4015,7 +4023,7 @@ } FREE_LOCK(&lk); } - tv = time; + getmicrotime(&tv); error = UFS_UPDATE(vp, &tv, &tv, MNT_WAIT); vput(vp); if (error) -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #0: Mon Mar 30 22:21:31 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Apr 6 23:33:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA03164 for freebsd-scsi-outgoing; Mon, 6 Apr 1998 23:33:46 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from revolution.3-cities.com (msmith@revolution.3-cities.com [204.203.224.155]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA03139 for ; Mon, 6 Apr 1998 23:33:39 -0700 (PDT) (envelope-from msmith@revolution.3-cities.com) Received: (from msmith@localhost) by revolution.3-cities.com (8.8.5/8.7.3) id XAA28712 for freebsd-scsi@freebsd.org; Mon, 6 Apr 1998 23:32:40 -0800 (PST) From: Mark D Smith Message-Id: <199804070732.XAA28712@revolution.3-cities.com> Subject: SCSI EOT fixed J"org? To: freebsd-scsi@FreeBSD.ORG Date: Mon, 6 Apr 1998 23:32:39 -0800 (PST) X-Mailer: ELM [version 2.4 PL25] 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 Greetings, Some time back, you answered a question in freebsd-scsi about end of tape detection on a DAT drive. You'd said that the message wasn't getting to the calling program through the kernel, or something similar. Has this been fixed or has the CAM (I STILL haven't tried it yet) code fixed it? thanks! Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Apr 7 12:39:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA23652 for freebsd-scsi-outgoing; Tue, 7 Apr 1998 12:39:47 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from heathers2.stdio.com (kyle@heathers2.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA23634 for ; Tue, 7 Apr 1998 12:39:45 -0700 (PDT) (envelope-from kyle@stdio.com) Received: (from kyle@localhost) by heathers2.stdio.com (8.8.8/8.8.8) id PAA04936; Tue, 7 Apr 1998 15:37:24 -0400 (EDT) Date: Tue, 7 Apr 1998 15:37:23 -0400 (EDT) From: Kyle McPeek To: freebsd-scsi@FreeBSD.ORG Subject: CAM Performance... 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 Hi All, For a project at work I need to be able to write 400MB sequentially to an Ultra-Wide harddisk (Seagate ST32171W 2GB) from an nfs mounted drive as fast a possible. right now we have it down to around 3:45 seconds using the old scsi code. I am using dd with bs=27163 (Approximately = data on one track) to write to /dev/rsd0s2c. Would the cam code improve sequential scsi writes? Also, what sort of general speed improvements has everyone seen using the cam code? I do still plan to test the cam code myself, but I would like to know what other people have experienced. Kyle McPeek TEKsystems Consultant at Lexmark International. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Apr 7 15:45:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09139 for freebsd-scsi-outgoing; Tue, 7 Apr 1998 15:45:06 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.213.32]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA09102 for ; Tue, 7 Apr 1998 15:44:57 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.82 #3) id 0yMgiI-0000V5-00; Tue, 7 Apr 1998 15:19:30 -0700 Date: Tue, 7 Apr 1998 15:19:29 -0700 (PDT) From: Tom To: Kyle McPeek cc: freebsd-scsi@FreeBSD.ORG Subject: Re: CAM Performance... In-Reply-To: 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 Tue, 7 Apr 1998, Kyle McPeek wrote: > Hi All, > > For a project at work I need to be able to write 400MB sequentially to an > Ultra-Wide harddisk (Seagate ST32171W 2GB) from an nfs mounted drive as > fast a possible. right now we have it down to around 3:45 seconds using > the old scsi code. > > I am using dd with bs=27163 (Approximately = data on one track) to write > to /dev/rsd0s2c. Why that block size? I think you will be much better with 64k blocks. How a particular drive organizes data to tracks is almost impossible to tell. Using a block size which is not a multiple of 512 almost certainly slows things down. Since you going for NFS to disk, is the bottleneck the disk or the network? If it is the disk, use two stripped drives for better performance. > Would the cam code improve sequential scsi writes? Also, what sort of > general speed improvements has everyone seen using the cam code? Probably not. CAMs main benefits are better error recovery, and better handling of lots of simultaneous i/o. Softupdates would improve things a lot for this application (esp if you have lots of RAM), but they don't work yet > I do still plan to test the cam code myself, but I would like to know > what other people have experienced. > > Kyle McPeek > TEKsystems Consultant at > Lexmark International. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Apr 8 08:18:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA17942 for freebsd-scsi-outgoing; Wed, 8 Apr 1998 08:18:18 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from heathers2.stdio.com (root@heathers2.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA17931 for ; Wed, 8 Apr 1998 08:18:10 -0700 (PDT) (envelope-from kyle@stdio.com) Received: (from kyle@localhost) by heathers2.stdio.com (8.8.8/8.8.8) id LAA17952; Wed, 8 Apr 1998 11:05:45 -0400 (EDT) Date: Wed, 8 Apr 1998 11:05:44 -0400 (EDT) From: Kyle McPeek To: Tom cc: freebsd-scsi@FreeBSD.ORG Subject: Re: CAM Performance... In-Reply-To: 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 Tom, I forgot to mention the nfs file server is a network appliance, raid 4 and very fast. Very few things I can do to tune it. I don't think any improvements can be found there, except maybe nfs V3? The network is all 100MB switched. I have tested both 10 and 100mb speeds and the transfer rate at 100mb is about twice that of 10mb. 10 MB seems to be slowed down by the network, but 100mb appears to be slowed down by the disk. The clients all have 64meg of memory. Would softupdates help on an unmounted partition? I will try 64K blocks. kyle. On Tue, 7 Apr 1998, Tom wrote: > > On Tue, 7 Apr 1998, Kyle McPeek wrote: > > > Hi All, > > > > For a project at work I need to be able to write 400MB sequentially to an > > Ultra-Wide harddisk (Seagate ST32171W 2GB) from an nfs mounted drive as > > fast a possible. right now we have it down to around 3:45 seconds using > > the old scsi code. > > > > I am using dd with bs=27163 (Approximately = data on one track) to write > > to /dev/rsd0s2c. > > Why that block size? I think you will be much better with 64k blocks. > How a particular drive organizes data to tracks is almost impossible to > tell. Using a block size which is not a multiple of 512 almost certainly > slows things down. > > Since you going for NFS to disk, is the bottleneck the disk or the > network? If it is the disk, use two stripped drives for better > performance. > > > Would the cam code improve sequential scsi writes? Also, what sort of > > general speed improvements has everyone seen using the cam code? > > Probably not. CAMs main benefits are better error recovery, and better > handling of lots of simultaneous i/o. > > Softupdates would improve things a lot for this application (esp if you > have lots of RAM), but they don't work yet > > > I do still plan to test the cam code myself, but I would like to know > > what other people have experienced. > > > > Kyle McPeek > > TEKsystems Consultant at > > Lexmark International. > > Tom > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Apr 8 09:55:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10372 for freebsd-scsi-outgoing; Wed, 8 Apr 1998 09:55:29 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.213.32]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA10325 for ; Wed, 8 Apr 1998 09:55:24 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.82 #3) id 0yMxjd-0001Py-00; Wed, 8 Apr 1998 09:30:01 -0700 Date: Wed, 8 Apr 1998 09:30:00 -0700 (PDT) From: Tom To: Kyle McPeek cc: freebsd-scsi@FreeBSD.ORG Subject: Re: CAM Performance... In-Reply-To: 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 Wed, 8 Apr 1998, Kyle McPeek wrote: > Tom, > > I forgot to mention the nfs file server is a network appliance, raid 4 > and very fast. Very few things I can do to tune it. I don't think any > improvements can be found there, except maybe nfs V3? > > The network is all 100MB switched. I have tested both 10 and 100mb > speeds and the transfer rate at 100mb is about twice that of 10mb. 10 MB > seems to be slowed down by the network, but 100mb appears to be slowed > down by the disk. Well, 100mbs should give you almost 10MB/s. Two Barracuda's stripped together should be able to almost that. > The clients all have 64meg of memory. Would softupdates help on an > unmounted partition? > I will try 64K blocks. Oh, raw partition. Softupdates won't help. 64k blocks will help a LOT then. The very small blocks you were using before would be slow and since it wasn't a multiple of 512 bytes, it would be somewhat inefficient. You probably want to strip two disks together and use the raw /dev/ccd0c device. A 16k or 32k strip size would probably be best for your application. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 9 03:34:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA06491 for freebsd-scsi-outgoing; Thu, 9 Apr 1998 03:34:13 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from tata.research.rockwell.cz (tata.research.rockwell.cz [193.85.154.66]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA06482 for ; Thu, 9 Apr 1998 03:34:01 -0700 (PDT) (envelope-from mira@rockwell.cz) Received: from rockwell.cz (aja.research.rockwell.cz [193.85.154.75]) by tata.research.rockwell.cz (8.6.9/8.6.5) with ESMTP id MAA02082 for ; Thu, 9 Apr 1998 12:42:38 +0200 Message-ID: <352CA660.2010112@rockwell.cz> Date: Thu, 09 Apr 1998 12:43:44 +0200 From: Miroslav Kes X-Mailer: Mozilla 4.03 [en] (WinNT; I) MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.ORG Subject: Adaptec aha 2940U2W ?? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi. I want to run FreeBSD on our new file server. The hardware specification is now subject of negotiation with our vendor. As we requested fast disk operations they offer us a Adaptec aha 2940 U2W controller. I was not sure about the support of this controller in FreeBSD (it's quite new) so I tried to search mailing lists. I found following (January 98): ------------------------------------------------------------------------------ From: Alex To: James Hokanson ... > Adaptec 2940UW (Ultra-Wide) SCSI controller Yes, the 2940 and all of its variants (except for the Ultra2 models) are well supported, and in fact have a mailing list dedicated to them. ------------------------------------------------------------------------------ My question is: What is the current status of the support for the Ultra2 models? If not how about the future (3.0 ??) ? Thanks a lot Mira -- ----------------------------------------------------------- | Miroslav Kes | |---------------------------------------------------------| | Rockwell Automation Ltd. | tel.: (+420) 2 2425 6913 | | Research Center Prague | fax: (+420) 2 250467 | | Americka 22 | e-mail: mira@rockwell.cz | | 120 00 Praha 2 - Vinohrady | | | Czech Republic | | ----------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 9 08:27:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA10179 for freebsd-scsi-outgoing; Thu, 9 Apr 1998 08:27:39 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA10174; Thu, 9 Apr 1998 08:27:36 -0700 (PDT) (envelope-from ip@albatross.mcc.ac.uk) Received: from albatross.mcc.ac.uk [130.88.202.16] by serenity.mcc.ac.uk with esmtp (Exim 1.81 #4) id 0yNJEi-0007m5-00; Thu, 9 Apr 1998 16:27:32 +0100 Received: (from ip@localhost) by albatross.mcc.ac.uk (8.8.8/8.8.4) id QAA09483; Thu, 9 Apr 1998 16:27:32 +0100 (BST) From: Ian Pallfreeman Message-Id: <199804091527.QAA09483@albatross.mcc.ac.uk> Subject: compression on Exabyte 8700LT? To: questions@FreeBSD.ORG, scsi@FreeBSD.ORG Date: Thu, 9 Apr 1998 16:27:31 +0100 (BST) Reply-To: ip@mcc.ac.uk X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've recently acquired another Exabyte drive, an 8700LT. This drive claims to be able to write 10Gb to a 112m tape in compressed mode, but I'm getting just the 5Gb I'd expect uncompressed. There are no switches other than the SCSI id on the box. The manual tells me to enable compression in software. ``mt -f /dev/rst1 comp 1'' logs the error "select returned an error of 5" to the console and gives me an I/O error from mt(1). How do I permanently enable compression? FreeBSD 3.0-CURRENT #9: Thu Apr 9 16:06:09 BST 1998 ip@lurch:/usr/src/sys/compile/LURCH [...] ahc0: rev 0x00 int a irq 9 on pci0.19.0 ahc0: aic7880 Single Channel, SCSI Id=7, 16/255 SCBs [...] st0 at scbus0 target 4 lun 0 st0: type 1 removable SCSI 2 st0: Sequential-Access density code 0x13, drive empty st1 at scbus0 target 5 lun 0 st1: type 1 removable SCSI 2 st1: Sequential-Access density code 0x0, drive empty TIA, Ian. -- Network Unit, SNOT Team, Manchester Computing, The University, Manchester, UK. mail: ip@mcc.ac.uk | phone: +44-161-275-6006 | fax: +44-161-275-6040 Where once we had dragons to slay, now we just sacrifice chickens. 35,000 users, 622Mb/s networking, and a 486. :-( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 9 09:27:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA04179 for freebsd-scsi-outgoing; Thu, 9 Apr 1998 09:27:57 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA04166 for ; Thu, 9 Apr 1998 09:27:54 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id KAA07550; Thu, 9 Apr 1998 10:26:53 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199804091626.KAA07550@panzer.plutotech.com> Subject: Re: compression on Exabyte 8700LT? In-Reply-To: <199804091527.QAA09483@albatross.mcc.ac.uk> from Ian Pallfreeman at "Apr 9, 98 04:27:31 pm" To: ip@mcc.ac.uk Date: Thu, 9 Apr 1998 10:26:53 -0600 (MDT) 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 Ian Pallfreeman wrote... > I've recently acquired another Exabyte drive, an 8700LT. This drive claims to > be able to write 10Gb to a 112m tape in compressed mode, but I'm getting just > the 5Gb I'd expect uncompressed. > > There are no switches other than the SCSI id on the box. The manual tells me > to enable compression in software. ``mt -f /dev/rst1 comp 1'' logs the error > "select returned an error of 5" to the console and gives me an I/O error from > mt(1). > > How do I permanently enable compression? > > FreeBSD 3.0-CURRENT #9: Thu Apr 9 16:06:09 BST 1998 > ip@lurch:/usr/src/sys/compile/LURCH > [...] > ahc0: rev 0x00 int a irq 9 on pci0.19.0 > ahc0: aic7880 Single Channel, SCSI Id=7, 16/255 SCBs > [...] > st0 at scbus0 target 4 lun 0 > st0: type 1 removable SCSI 2 > st0: Sequential-Access density code 0x13, drive empty > st1 at scbus0 target 5 lun 0 > st1: type 1 removable SCSI 2 > st1: Sequential-Access density code 0x0, drive empty Well, this may be fixed by PR kern/5274. Basically, the page format bit isn't being set when a mode select is done on the drive, so the drive probably thinks it's a SCSI-1 mode select, and doesn't pay attention to the compression page. So, you might want to try applying the patch in that PR, and see if it fixes your problem. Most drives I've seen come with compression turned on by default, but maybe yours doesn't. The next CAM snapshot fixes this. (at least on the 6 tape drives I've tested it on) mt(1) will tell you whether compression is supported or turned on for your drive. (and which type of compression is in use) For instance: sa0 at ahc0 bus 0 target 5 lun 0 sa0: Removable Sequential Access SCSI2 device sa0: 5.0MB/s transfers (5.0MHz, offset 15) {bladerunner:/usr/home/ken:4:0} mt status Mode Density Blocksize bpi Compression Current: X3B5/88-185A 512 bytes 61000 unsupported ---------available modes--------- 0: X3B5/88-185A 512 bytes 61000 unsupported 1: X3B5/88-185A 512 bytes 61000 unsupported 2: X3B5/88-185A 512 bytes 61000 unsupported 3: X3B5/88-185A 512 bytes 61000 unsupported sa1 at ahc1 bus 0 target 4 lun 0 sa1: Removable Sequential Access SCSI2 device sa1: Serial Number 00263194 sa1: 4.32MB/s transfers (4.32MHz, offset 11) {bladerunner:/usr/home/ken:7:0} mt -f /dev/nrsa1 status Mode Density Blocksize bpi Compression Current: 0x00 1024 bytes 0 unsupported ---------available modes--------- 0: 0x00 1024 bytes 0 unsupported 1: 0x00 1024 bytes 0 unsupported 2: 0x00 1024 bytes 0 unsupported 3: 0x00 1024 bytes 0 unsupported sa2 at adv1 bus 0 target 2 lun 0 sa2: Removable Sequential Access SCSI2 device sa2: Serial Number 16012000 sa2: 5.0MB/s transfers (5.0MHz, offset 15) {bladerunner:/usr/home/ken:9:0} mt -f /dev/nrsa2 status Mode Density Blocksize bpi Compression Current: 0x00 1024 bytes 0 IDRC ---------available modes--------- 0: 0x00 1024 bytes 0 IDRC 1: 0x00 1024 bytes 0 IDRC 2: 0x00 1024 bytes 0 IDRC 3: 0x00 1024 bytes 0 IDRC sa0 at ahc0 bus 0 target 5 lun 0 sa0: Removable Sequential Access SCSI2 device sa0: 5.0MB/s transfers (5.0MHz, offset 8) {thunderdome:/usr/home/ken:5:0} mt status Mode Density Blocksize bpi Compression Current: X3B5/88-185A 512 bytes 61000 DCLZ ---------available modes--------- 0: X3B5/88-185A 512 bytes 61000 DCLZ 1: X3B5/88-185A 512 bytes 61000 DCLZ 2: X3B5/88-185A 512 bytes 61000 DCLZ 3: X3B5/88-185A 512 bytes 61000 DCLZ For some reason, Exabyte drives don't like to report any density information. Go figure. 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 Thu Apr 9 11:46:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20824 for freebsd-scsi-outgoing; Thu, 9 Apr 1998 11:46:17 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from tharg.eu.org (ipallfreeman.cwcmultimedia.co.uk [195.44.34.165]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20816 for ; Thu, 9 Apr 1998 11:46:15 -0700 (PDT) (envelope-from ip@tharg.eu.org) Received: (from ip@localhost) by tharg.eu.org (8.8.8/8.7.3) id TAA27371; Thu, 9 Apr 1998 19:45:34 +0100 (BST) From: Ian Pallfreeman Message-Id: <199804091845.TAA27371@tharg.eu.org> Subject: Re: compression on Exabyte 8700LT? In-Reply-To: <199804091626.KAA07550@panzer.plutotech.com> from "Kenneth D. Merry" at "Apr 9, 98 10:26:53 am" To: ken@plutotech.com (Kenneth D. Merry) Date: Thu, 9 Apr 1998 19:45:34 +0100 (BST) Cc: ip@mcc.ac.uk, scsi@FreeBSD.ORG Reply-To: ip@mcc.ac.uk 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 Ken Merry wrote: > Ian Pallfreeman wrote... > > [...] > > How do I permanently enable compression? > > [...] > Well, this may be fixed by PR kern/5274. > [...] > So, you might want to try applying the patch in that PR, and see if > it fixes your problem. Sorry -- I didn't mention that I'd already found that and applied it, before squeaking to the mailing lists. > Most drives I've seen come with compression turned > on by default, but maybe yours doesn't. No, the cursed thing doesn't. I'd assumed it would. The "estimated N tape blocks" numbers from the dump logs add up, though -- it's only writing 5GB. > The next CAM snapshot fixes this. Thanks! Can't spare the hardware to try it right now, but the new repository and ftp mirror is in the orderbook... Cheers, Ian. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 9 18:54:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA25613 for freebsd-scsi-outgoing; Thu, 9 Apr 1998 18:54:31 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA25594; Thu, 9 Apr 1998 18:54:21 -0700 (PDT) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id LAA16680; Fri, 10 Apr 1998 11:24:09 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id LAA00741; Fri, 10 Apr 1998 11:24:08 +0930 (CST) (envelope-from grog) Message-ID: <19980410112408.01873@freebie.lemis.com> Date: Fri, 10 Apr 1998 11:24:08 +0930 From: Greg Lehey To: ip@mcc.ac.uk, questions@FreeBSD.ORG, scsi@FreeBSD.ORG, FreeBSD current users Subject: Re: compression on Exabyte 8700LT? Reply-To: FreeBSD current users References: <199804091527.QAA09483@albatross.mcc.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199804091527.QAA09483@albatross.mcc.ac.uk>; from Ian Pallfreeman on Thu, Apr 09, 1998 at 04:27:31PM +0100 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 9 April 1998 at 16:27:31 +0100, Ian Pallfreeman wrote: > I've recently acquired another Exabyte drive, an 8700LT. This drive claims to > be able to write 10Gb to a 112m tape in compressed mode, but I'm getting just > the 5Gb I'd expect uncompressed. > > ... > > FreeBSD 3.0-CURRENT #9: Thu Apr 9 16:06:09 BST 1998 > ip@lurch:/usr/src/sys/compile/LURCH Please don't discuss CURRENT topics on -questions. Send them to -current instead (to which I hope you are subscribed). I'm copying -questions on this reply only to show where I've sent the thread. I think there's a general problem with tape compression under -CURRENT. A few months back, I used to be able to back up a complete 8 GB on my DDS-2 drives, but now I've done some testing and found it gives up somewhere round 3.4 GB. I don't understand that, since the native tape capacity is 4 GB. -CURRENT people: I'm using the old SCSI driver. The tape is set to start up in compressed mode, and the DC LED is illuminated all the time. This looks to me as if something in the driver is explicitly disabling compression, or just possibly that the driver is guessing the size of the tape and stopping (with EIO) when it reaches this point. The other point is that it's still returning EIO. I know there's been some discussion about this before, and ISTR that it was inconclusive ("that's the way our grandfathers did it"). While looking at the problem, I came across a program I wrote in my BSD/OS days back in 1992, and I note that even then BSD/OS returned ENOSPC when it got to the end of the tape. This makes a whole lot more sense, and it obviously seems to have withstood the test of time. How about it? Would I get an improvement on either of these points if I installed CAM? I know that CAM can't handle compression switching yet, but can it do compression if it's enabled on the drive? Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 9 20:18:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA14216 for freebsd-scsi-outgoing; Thu, 9 Apr 1998 20:18:35 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA14211 for ; Thu, 9 Apr 1998 20:18:33 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.8.7/8.6.12) id DAA00661; Fri, 10 Apr 1998 03:18:29 GMT Message-ID: <19980409201829.36529@nuxi.com> Date: Thu, 9 Apr 1998 20:18:29 -0700 From: "David O'Brien" To: scsi@FreeBSD.ORG Subject: Re: compression on Exabyte 8700LT? Reply-To: obrien@NUXI.com References: <199804091527.QAA09483@albatross.mcc.ac.uk> <19980410112408.01873@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <19980410112408.01873@freebie.lemis.com>; from Greg Lehey on Fri, Apr 10, 1998 at 11:24:08AM +0930 X-Warning: Mutt Bites! X-Operating-System: FreeBSD 2.2.5-STABLE Organization: The NUXI *BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Apr 10, 1998 at 11:24:08AM +0930, Greg Lehey wrote: > I think there's a general problem with tape compression under > -CURRENT. A few months back, I used to be able to back up a complete > 8 GB on my DDS-2 drives, but now I've done some testing and found it > gives up somewhere round 3.4 GB. I don't understand that, since the > native tape capacity is 4 GB. Hum.. I wonder if -STABLE has the same problem. About a month ago my HP 4mm tape could only backup 1.8gig when the native capacity is 2gig and I have backed up 2gig in the past. -- David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 9 21:53:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA09048 for freebsd-scsi-outgoing; Thu, 9 Apr 1998 21:53:03 -0700 (PDT) (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 VAA09043; Thu, 9 Apr 1998 21:53:01 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id WAA16931; Thu, 9 Apr 1998 22:49:14 -0600 (MDT) Date: Thu, 9 Apr 1998 22:49:14 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199804100449.WAA16931@narnia.plutotech.com> To: FreeBSD current users cc: FreeBSD-scsi@FreeBSD.ORG Subject: Re: compression on Exabyte 8700LT? Newsgroups: pluto.freebsd.scsi In-Reply-To: <199804091527.QAA09483@albatross.mcc.ac.uk> <19980410112408.01873@freebie.lemis.com> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I don't know why this was sent to questions. It was started on SCSI which seems to be where it belongs... > -CURRENT people: I'm using the old SCSI driver. The tape is set to > start up in compressed mode, and the DC LED is illuminated all the > time. This looks to me as if something in the driver is explicitly > disabling compression, or just possibly that the driver is guessing > the size of the tape and stopping (with EIO) when it reaches this > point. Neither the old driver, nor the CAM driver performs any type of guessing about the size of the tape. > The other point is that it's still returning EIO. I know there's been > some discussion about this before, and ISTR that it was inconclusive > ("that's the way our grandfathers did it"). While looking at the > problem, I came across a program I wrote in my BSD/OS days back in > 1992, and I note that even then BSD/OS returned ENOSPC when it got to > the end of the tape. This makes a whole lot more sense, and it > obviously seems to have withstood the test of time. How about it? The decision was that it should return ENOSPC. The CAM driver does return ENOSPC. I have patches, in my CAM tree, to ensure that dump and restore correctly deal with ENOSPC as an EOT condition. Someone should probably check pax, cpio, and tar. > Would I get an improvement on either of these points if I installed > CAM? Probably. You may want to wait for the weekend though. I'm "this close" to finishing the BusLogic driver, and I intend to release a new snapshot at that time. This will also include some improvements to the tape driver. > I know that CAM can't handle compression switching yet, but can > it do compression if it's enabled on the drive? The next snapshot will have compression and density control support. Ken's already implemented, and tested it. > Greg -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 9 22:23:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA17092 for freebsd-scsi-outgoing; Thu, 9 Apr 1998 22:23:45 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA17087 for ; Thu, 9 Apr 1998 22:23:44 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id XAA10189; Thu, 9 Apr 1998 23:23:29 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199804100523.XAA10189@panzer.plutotech.com> Subject: Re: compression on Exabyte 8700LT? In-Reply-To: <19980410112408.01873@freebie.lemis.com> from Greg Lehey at "Apr 10, 98 11:24:08 am" To: grog@lemis.com Date: Thu, 9 Apr 1998 23:23:29 -0600 (MDT) Cc: ip@mcc.ac.uk, 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 [ lists trimmed to just -SCSI, where this thread really belongs ] Greg Lehey wrote... > On Thu, 9 April 1998 at 16:27:31 +0100, Ian Pallfreeman wrote: > > I've recently acquired another Exabyte drive, an 8700LT. This drive claims to > > be able to write 10Gb to a 112m tape in compressed mode, but I'm getting just > > the 5Gb I'd expect uncompressed. > > > > ... > > > > FreeBSD 3.0-CURRENT #9: Thu Apr 9 16:06:09 BST 1998 > > ip@lurch:/usr/src/sys/compile/LURCH [ ... ] > I think there's a general problem with tape compression under > -CURRENT. A few months back, I used to be able to back up a complete > 8 GB on my DDS-2 drives, but now I've done some testing and found it > gives up somewhere round 3.4 GB. I don't understand that, since the > native tape capacity is 4 GB. It does sound sort of like compression is off. > -CURRENT people: I'm using the old SCSI driver. The tape is set to > start up in compressed mode, and the DC LED is illuminated all the > time. This looks to me as if something in the driver is explicitly > disabling compression, or just possibly that the driver is guessing > the size of the tape and stopping (with EIO) when it reaches this > point. That certainly sounds odd. I haven't explored the -current tape driver enough to know which might be the case. Since the data comrpession light is on, I'd guess that compression really is enabled... > The other point is that it's still returning EIO. I know there's been > some discussion about this before, and ISTR that it was inconclusive > ("that's the way our grandfathers did it"). While looking at the > problem, I came across a program I wrote in my BSD/OS days back in > 1992, and I note that even then BSD/OS returned ENOSPC when it got to > the end of the tape. This makes a whole lot more sense, and it > obviously seems to have withstood the test of time. How about it? The CAM tape driver (at least the one in our development tree) returns ENOSPC when it reaches the end of a tape. dump and restore in the CAM tree have been patched to recognize that as an end of tape signal. > Would I get an improvement on either of these points if I installed > CAM? I know that CAM can't handle compression switching yet, but can > it do compression if it's enabled on the drive? Wait until the next CAM snapshot, and I think both of these will improve for you. You will be able to tell from mt(1) whether your drive is capable of compression, and if so, whether it is enabled. If it is enabled, mt will tell you which algorithm is in use. You can also enable and disable compression. I have successfully tested it on two different Archive Python drives (DDS-1 and DDS-2), a Sony SDT-5000, an Exabyte 8200, Exabyte 8500 and an Exabyte Eliant. I believe it should work with most any drive. (Well, okay, I haven't tried it with any Tandberg drives...) As far as when the next snapshot will be out...I believe Justin wants to get the BusLogic driver solidified before he makes the snap. I think the driver is in good shape now, but I would be foolish to make any promises on when the snapshot will come out. 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 Thu Apr 9 22:46:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA23550 for freebsd-scsi-outgoing; Thu, 9 Apr 1998 22:46:42 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA23530; Thu, 9 Apr 1998 22:46:37 -0700 (PDT) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id PAA16901; Fri, 10 Apr 1998 15:16:33 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id PAA01558; Fri, 10 Apr 1998 15:16:33 +0930 (CST) (envelope-from grog) Message-ID: <19980410151633.34010@freebie.lemis.com> Date: Fri, 10 Apr 1998 15:16:33 +0930 From: Greg Lehey To: "Justin T. Gibbs" , FreeBSD current users Cc: FreeBSD-scsi@FreeBSD.ORG Subject: Re: compression on Exabyte 8700LT? References: <199804091527.QAA09483@albatross.mcc.ac.uk> <199804100449.WAA16931@narnia.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199804100449.WAA16931@narnia.plutotech.com>; from Justin T. Gibbs on Thu, Apr 09, 1998 at 10:49:14PM -0600 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 9 April 1998 at 22:49:14 -0600, Justin T. Gibbs wrote: > I don't know why this was sent to questions. It was started on SCSI > which seems to be where it belongs... I saw it on -scsi and -questions. Since it related to -current, I followed up there. The copy to -questions was a one-off to tell people where it had gone. >> -CURRENT people: I'm using the old SCSI driver. The tape is set to >> start up in compressed mode, and the DC LED is illuminated all the >> time. This looks to me as if something in the driver is explicitly >> disabling compression, or just possibly that the driver is guessing >> the size of the tape and stopping (with EIO) when it reaches this >> point. > > Neither the old driver, nor the CAM driver performs any type of guessing > about the size of the tape. I didn't think so. I was just wondering why the capacity was so much less than the nominal capacity. >> The other point is that it's still returning EIO. I know there's been >> some discussion about this before, and ISTR that it was inconclusive >> ("that's the way our grandfathers did it"). While looking at the >> problem, I came across a program I wrote in my BSD/OS days back in >> 1992, and I note that even then BSD/OS returned ENOSPC when it got to >> the end of the tape. This makes a whole lot more sense, and it >> obviously seems to have withstood the test of time. How about it? > > The decision was that it should return ENOSPC. The CAM driver does > return ENOSPC. I have patches, in my CAM tree, to ensure that dump > and restore correctly deal with ENOSPC as an EOT condition. Good. > Someone should probably check pax, cpio, and tar. I'll definitely check tar. >> Would I get an improvement on either of these points if I installed >> CAM? > > Probably. You may want to wait for the weekend though. I'm "this close" > to finishing the BusLogic driver, and I intend to release a new snapshot > at that time. This will also include some improvements to the tape > driver. Good. I'll do that. Is it now in -CURRENT? >> I know that CAM can't handle compression switching yet, but can >> it do compression if it's enabled on the drive? > > The next snapshot will have compression and density control support. > Ken's already implemented, and tested it. Great Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 10 17:28:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA24099 for freebsd-scsi-outgoing; Fri, 10 Apr 1998 17:28:51 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from onyx.southwind.net (root@onyx.southwind.net [206.53.103.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA24043 for ; Fri, 10 Apr 1998 17:28:41 -0700 (PDT) (envelope-from fclark@southwind.net) Received: from southwind.net (ict91.southwind.net [206.53.100.91]) by onyx.southwind.net (8.8.8/8.8.8) with ESMTP id TAA23702 for ; Fri, 10 Apr 1998 19:28:35 -0500 (CDT) Message-ID: <352EB966.3B960D54@southwind.net> Date: Fri, 10 Apr 1998 19:29:26 -0500 From: Fred Clark X-Mailer: Mozilla 4.04 [en] (Win95; U) MIME-Version: 1.0 To: FreeBSD SCSI Subject: Can't access tape drive with tar, with an Adaptec 2940UW Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I recently install a current snapshot dated 2/22/98. Whenever I try to retreive any information from the tape drive (/dev/rst0) using tar (i.e. tar tvf, xvf, etc..), I receive a message from tar "tar: blocksize=1". There's no problem with the device accessing the drive, it reads the tape. The drive works fine on another machine running 2.2.5, (read and write accessing). As mentioned in the subject line, i'm using an Adaptec 2940UW with a MaynardStream 1350q tape drive. This is the first time i've ever encountered this problem, any pointers. Thanks, Fred... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Apr 11 00:22:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA25184 for freebsd-scsi-outgoing; Sat, 11 Apr 1998 00:22:16 -0700 (PDT) (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 AAA25138 for ; Sat, 11 Apr 1998 00:22:04 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id JAA08901; Sat, 11 Apr 1998 09:22:01 +0200 (CEST) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id IAA14596; Sat, 11 Apr 1998 08:52:22 +0200 (MET DST) Message-ID: <19980411085222.04906@uriah.heep.sax.de> Date: Sat, 11 Apr 1998 08:52:22 +0200 From: J Wunsch To: freebsd-scsi@FreeBSD.ORG Cc: Donald Burr Subject: Re: which CD-R derives are supported by worm driver? Reply-To: Joerg Wunsch References: <351d1b70.809499@mail.inreach.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <351d1b70.809499@mail.inreach.com>; from Donald Burr on Sat, Mar 28, 1998 at 03:49:23PM +0000 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 Donald Burr wrote: > Which SCSI CD-R (recordable and/or rewritable) devices are supported > by FreeBSD's worm driver? This information used to be in wormcontrol(8) (which is arguably the wrong place), but vanished there with Jean-Marc's device ID based auto-recognition. The current list can be obtained by: j@uriah 535% grep 'T_WORM.*T_REMOV' /sys/scsi/scsiconf.c T_READONLY, T_WORM, T_REMOV, "HP", "C4324/C4325", "*", T_READONLY, T_WORM, T_REMOV, "HP", "CD-Writer 6020", "*", T_READONLY, T_WORM, T_REMOV, "IMS", "CDD2000*", "*", T_READONLY, T_WORM, T_REMOV, "PHILIPS", "CDD2*", "*", T_READONLY, T_WORM, T_REMOV, "PLASMON", "RF41*", "*", T_WORM, T_WORM, T_REMOV, "*", "*", "*", This assumes you're asking for which drives are being supported in `native' mode, i. e. by wormcontrol(8) & Co. Other drives not mentioned above might be caught in scsiconf.c by the last clause above, but are not usable directly (i. e. through write(2) syscalls). Nevertheless, they might work in connection with third-party software like cdrecord (it's in the ports collection). The latter is probably better maintained than worm(4), but does everything and all in userland, violating the ``classic Unix layering''. -- 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 Sat Apr 11 06:14:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA29931 for freebsd-scsi-outgoing; Sat, 11 Apr 1998 06:14:36 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA29902 for ; Sat, 11 Apr 1998 06:14:34 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) Received: from salomon.mchp.siemens.de (salomon.siemens.de [139.23.33.13]) by david.siemens.de (8.8.8/8.8.8) with ESMTP id PAA22975 for ; Sat, 11 Apr 1998 15:14:20 +0200 (MDT) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from curry.mchp.siemens.de (daemon@curry.mchp.siemens.de [146.180.31.23]) by salomon.mchp.siemens.de (8.8.8/8.8.5) with ESMTP id PAA29421 for ; Sat, 11 Apr 1998 15:14:21 +0200 (MDT) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.8/8.8.8) id PAA00722 for ; Sat, 11 Apr 1998 15:14:21 +0200 (CEST) From: Andre Albsmeier Message-Id: <199804111314.PAA28884@intern> Subject: Which FreeBSD version supports this new 3940AU? To: freebsd-scsi@FreeBSD.ORG Date: Sat, 11 Apr 1998 15:14:18 +0200 (CEST) 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 Hi, yesterday I received the Adaptec 3940 controller I ordered a while ago. It is called exactly 3940AU and carries only one big chip on it. On the box still is a picture of the 3940U which has 3 chips on it - 2 x 7880 and one DEC chip (PCI bridge?). Now the problem is, it doesn't get detected by FreeBSD 2.2.6, but the two 2940U are being detected properly. I think, Adaptec has changed something while integrating the 3 chips into one. Is there a known workaround here? Or will the (hopefully) upcoming CAM driver support this new beast? Thanks, -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Apr 11 12:03:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17865 for freebsd-scsi-outgoing; Sat, 11 Apr 1998 12:03:05 -0700 (PDT) (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 MAA17754 for ; Sat, 11 Apr 1998 12:01:06 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id UAA09089; Sat, 11 Apr 1998 20:52:29 +0200 (CEST) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id UAA16099; Sat, 11 Apr 1998 20:46:17 +0200 (MET DST) Message-ID: <19980411204617.63713@uriah.heep.sax.de> Date: Sat, 11 Apr 1998 20:46:17 +0200 From: J Wunsch To: freebsd-scsi@FreeBSD.ORG Cc: Mark D Smith Subject: Re: SCSI EOT fixed J"org? Reply-To: Joerg Wunsch References: <199804070732.XAA28712@revolution.3-cities.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199804070732.XAA28712@revolution.3-cities.com>; from Mark D Smith on Mon, Apr 06, 1998 at 11:32:39PM -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 Mark D Smith wrote: > Some time back, you answered a question in freebsd-scsi about end of > tape detection on a DAT drive. You'd said that the message wasn't > getting to the calling program through the kernel, or something > similar. Has this been fixed or has the CAM (I STILL haven't tried > it yet) code fixed it? AFAIK, neither subsystem handles tape EOFs correctly yet. (To recall the problem: the driver is supposed to return a `short write' (even null write) in case it encounters EOF/EOM, but instead it returns EIO currently). -- 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 Sat Apr 11 12:22:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA20385 for freebsd-scsi-outgoing; Sat, 11 Apr 1998 12:22:18 -0700 (PDT) (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 MAA20371 for ; Sat, 11 Apr 1998 12:22:11 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id VAA09546; Sat, 11 Apr 1998 21:22:02 +0200 (CEST) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id VAA16398; Sat, 11 Apr 1998 21:16:57 +0200 (MET DST) Message-ID: <19980411211657.59410@uriah.heep.sax.de> Date: Sat, 11 Apr 1998 21:16:57 +0200 From: J Wunsch To: freebsd-scsi@FreeBSD.ORG Cc: "Larry S. Marso" Subject: Re: scanner--*anyone* successful with FreeBSD? Reply-To: Joerg Wunsch References: <19980403081559.64189@marso.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <19980403081559.64189@marso.com>; from Larry S. Marso on Fri, Apr 03, 1998 at 08:15:59AM -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 Larry S. Marso wrote: > I am wondering whether *anyone* has a scanner working in the FreeBSD > environment, or if it's only a fool's (or a superlative hacker's) quest > at the moment. I'm struggling with a brand-spanking new HP6100cse. I'm using an HP ScanJet 4C regularly. However, i'm using it on a decent SCSI controller (AHA2940). The aic(4) driver is known to be rather weak (nobody maintains this driver by now), so i wouldn't be surprised if _that_ were the root of your evil. -- 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 Sat Apr 11 12:22:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA20445 for freebsd-scsi-outgoing; Sat, 11 Apr 1998 12:22:33 -0700 (PDT) (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 MAA20422 for ; Sat, 11 Apr 1998 12:22:31 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id VAA09554; Sat, 11 Apr 1998 21:22:25 +0200 (CEST) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id VAA16410; Sat, 11 Apr 1998 21:18:35 +0200 (MET DST) Message-ID: <19980411211834.44203@uriah.heep.sax.de> Date: Sat, 11 Apr 1998 21:18:34 +0200 From: J Wunsch To: freebsd-scsi@FreeBSD.ORG Cc: "Bryan K. Ogawa" , Malte Lance Subject: Re: Will a termination problem cause total hangs? Reply-To: Joerg Wunsch References: <3.0.32.19980403113026.007430fc@cyclone.degnet.baynet.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: ; from Bryan K. Ogawa on Fri, Apr 03, 1998 at 12:37:46PM -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 Bryan K. Ogawa wrote: > Can a termination problem cause total kernel hangs? Sure, if it jams a SCSI controller (or driver) so processes trying to access SCSI disks will hang in `disk wait' status. -- 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 Sat Apr 11 14:25:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09967 for freebsd-scsi-outgoing; Sat, 11 Apr 1998 14:25:30 -0700 (PDT) (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 OAA09962; Sat, 11 Apr 1998 14:25:27 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id XAA11294; Sat, 11 Apr 1998 23:25:24 +0200 (CEST) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id XAA16570; Sat, 11 Apr 1998 23:12:48 +0200 (MET DST) Message-ID: <19980411231247.52126@uriah.heep.sax.de> Date: Sat, 11 Apr 1998 23:12:47 +0200 From: J Wunsch To: freebsd-scsi@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Cc: Julie Juracich Subject: Re: Problems with Adaptec2920 driver Reply-To: Joerg Wunsch References: <199804050645.WAA08022@grue.xaqti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199804050645.WAA08022@grue.xaqti.com>; from Julie Juracich on Sat, Apr 04, 1998 at 10:45:33PM -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 Julie Juracich wrote: > I have now gone to FreeBSD-CURRENT, and I have tried both that driver > and the patch located here: > ftp://ftp.freebsd.org/pub/FreeBSD/2.2.6-RELEASE/xperimnt/aha2920/tmc18c30-sysdif > f.gz (Btw., your mailer spams long lines. Better replace it.) Sorry, as you can see, i've once hacked this driver kit for 2.2-stable (by the time 2.2.5 has been prepared). While i have been gradually upgrading my -current spam box with this driver enabled, recently it failed compilation with the same problems you are seeing. I haven't found the time yet to even look at what the problems are. (Well, i made a glance on them, but couldn't find the reason within 5 minutes, so i gave up and disabled ahd(4) on this box, in order to get a compilable -current kernel at all.) ahd(4) definately needs someone who'd adopt this baby. Anyway, IMHO it needs some restructuring and ``FreeBSDization'' before getting imported. Also, whoever would like to pick up that job, should be prepared to assist Justin in moving the driver into CAM. I'm definately and ultimately completely out of time for this job. (I've still got one of those cards, and could do testing however.) -- 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 Sat Apr 11 16:04:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA26816 for freebsd-scsi-outgoing; Sat, 11 Apr 1998 16:04:16 -0700 (PDT) (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 QAA26810 for ; Sat, 11 Apr 1998 16:04:15 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id QAA08634; Sat, 11 Apr 1998 16:59:29 -0600 (MDT) Date: Sat, 11 Apr 1998 16:59:29 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199804112259.QAA08634@narnia.plutotech.com> To: Andre Albsmeier cc: scsi@FreeBSD.ORG Subject: Re: Which FreeBSD version supports this new 3940AU? Newsgroups: pluto.freebsd.scsi In-Reply-To: <199804111314.PAA28884@intern> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <199804111314.PAA28884@intern> you wrote: > Is there a known workaround here? Or will the (hopefully) > upcoming CAM driver support this new beast? The CAM driver supports the aic7895 which is the "one large chip" on a 3940AU. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Apr 11 18:27:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA18680 for freebsd-scsi-outgoing; Sat, 11 Apr 1998 18:27:59 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA18675 for ; Sat, 11 Apr 1998 18:27:56 -0700 (PDT) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id KAA21793; Sun, 12 Apr 1998 10:57:36 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id KAA22660; Sun, 12 Apr 1998 10:57:35 +0930 (CST) (envelope-from grog) Message-ID: <19980412105735.37665@freebie.lemis.com> Date: Sun, 12 Apr 1998 10:57:35 +0930 From: Greg Lehey To: Joerg Wunsch , freebsd-scsi@FreeBSD.ORG Cc: Mark D Smith Subject: Re: SCSI EOT fixed J"org? References: <199804070732.XAA28712@revolution.3-cities.com> <19980411204617.63713@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19980411204617.63713@uriah.heep.sax.de>; from J Wunsch on Sat, Apr 11, 1998 at 08:46:17PM +0200 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 11 April 1998 at 20:46:17 +0200, J Wunsch wrote: > As Mark D Smith wrote: > >> Some time back, you answered a question in freebsd-scsi about end of >> tape detection on a DAT drive. You'd said that the message wasn't >> getting to the calling program through the kernel, or something >> similar. Has this been fixed or has the CAM (I STILL haven't tried >> it yet) code fixed it? > > AFAIK, neither subsystem handles tape EOFs correctly yet. (To recall > the problem: the driver is supposed to return a `short write' (even > null write) in case it encounters EOF/EOM, but instead it returns EIO > currently). My understanding is that the CAM driver returns ENOSPC. I don't know whether it performs a partial write, but as long as it correctly reports what it does, that's fine by me. -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Apr 11 23:42:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28332 for freebsd-scsi-outgoing; Sat, 11 Apr 1998 23:42:33 -0700 (PDT) (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 XAA28324 for ; Sat, 11 Apr 1998 23:42:31 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id IAA18113 for freebsd-scsi@FreeBSD.ORG; Sun, 12 Apr 1998 08:42:29 +0200 (CEST) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id IAA21498; Sun, 12 Apr 1998 08:39:37 +0200 (MET DST) Message-ID: <19980412083937.23967@uriah.heep.sax.de> Date: Sun, 12 Apr 1998 08:39:37 +0200 From: J Wunsch To: freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI EOT fixed J"org? Reply-To: Joerg Wunsch References: <199804070732.XAA28712@revolution.3-cities.com> <19980411204617.63713@uriah.heep.sax.de> <19980412105735.37665@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <19980412105735.37665@freebie.lemis.com>; from Greg Lehey on Sun, Apr 12, 1998 at 10:57:35AM +0930 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 Greg Lehey wrote: > My understanding is that the CAM driver returns ENOSPC. I don't know > whether it performs a partial write, but as long as it correctly > reports what it does, that's fine by me. I don't care what's fine by you. :) ENOSPC is equally wrong as EIO. EOF/EOM _must_ return a partial write, *and no error*. Anything else breaks the Unix semantics, and thus all programs that rely on Unix semantics (dump(8), multi-volume tar(1)). An error must only be returned iff attempting to start the write operation beyond the end of medium. Since tapes cannot seek (at least not in the current driver, although it's probably possible for some drives to teach them seeking), the question is not so easy to answer when you really have to return an error. I think the following would be OK for all the existing software: . write(2) starts before EOM, but the requests spans EOM: the syscall writes as much as can be handled, and returns a short write (but no error). . first write(2) request that starts exactly at EOM: special case of the above, the syscall returns just 0, but no error. . repeated attempt of the previous case: return EINVAL. The latter would help programs that attempt to repeatedly to operate beyond the EOM to detect their error, albeit these programs are arguably broken. For read(2) syscalls, things similarly apply to each single tape file, but IMHO there's no EOM detection required, only detection of EOF on each tape file. A repeated attempt to read beyond the EOF of one tape file should however advance to the next tape file if possible, and only yield an error iff no more tape files are available. I think tape driver semantics slightly differ in this behaviour across the various Unix systems. :( -- 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