From owner-freebsd-hackers Thu Apr 18 15:52:30 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA15323 for hackers-outgoing; Thu, 18 Apr 1996 15:52:30 -0700 (PDT) Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA15314 Thu, 18 Apr 1996 15:52:27 -0700 (PDT) Message-Id: <199604182252.PAA15314@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol To: Jaye Mathisen cc: hackers@freebsd.org, gibbs@freebsd.org Subject: Re: QUEUE_FULL_ENABLE option really work? In-reply-to: Your message of "Thu, 18 Apr 1996 15:12:53 PDT." Date: Thu, 18 Apr 1996 15:52:27 -0700 From: "Justin T. Gibbs" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >Hmmm, well, my bonnie numbers didn't change much at all, and i was getting >"QUEUE Full" messages on my console, which have disappeared. Now if I can >get rid of the FS corruption on my 2940UW, I'll be a happy camper. (From >another message). You didn't mention that you were getting "QUEUE Full" messages on the console. The reason that the QUEUE_FULL_SUPPORTED define is in there is because we don't really handle Queue full status (that will change in the next day or two), but some people still use it because their drives have deep enough queues that they can use the additional tags safely. What kind of drive are you using? If its your RAID box, are you using multiple luns at once? (The number of tags to use is per lun, not per device.) -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations ===========================================