From owner-freebsd-hackers Thu Nov 20 23:20:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA19319 for hackers-outgoing; Thu, 20 Nov 1997 23:20:45 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA19314 for ; Thu, 20 Nov 1997 23:20:39 -0800 (PST) (envelope-from mrcpu@cdsnet.net) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id XAA28632; Thu, 20 Nov 1997 23:20:28 -0800 (PST) Date: Thu, 20 Nov 1997 23:20:28 -0800 (PST) From: Jaye Mathisen To: "Jordan K. Hubbard" cc: hackers@FreeBSD.ORG Subject: Re: Serious performance issue with 2.2.5-RELEASE In-Reply-To: <1925.880090601@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Pulleeze... I've been running practically every release of 2.2.x on almost 30 servers on a more regular basis than probably anybody. This is the only machine having the problem, and it ran 2.2.2 just yippee skippee. The problem started 10 minutes after 2.2.5 went in, and I'm having a hard time believing that it could be anything else, when there's no other failure mode (like smoke, disk problems, ethernet interface problems, or anything else). I have restored part of the backups to get to a usable 2.2.2, and it boots and runs just fine. Given that John even points out that there are bugs in the vfs_bio code that weren't in 2.2.2, I find it hard not to point the finger a bit at 2.2.5. In any case, I will try the 2 patches I got and see what happens. It definitely appears load related.