From owner-freebsd-stable Mon Jan 7 11:11:29 2002 Delivered-To: freebsd-stable@freebsd.org Received: from enigma.trueimpact.net (enigma.trueimpact.net [209.82.45.201]) by hub.freebsd.org (Postfix) with ESMTP id 2807737B41A; Mon, 7 Jan 2002 11:11:26 -0800 (PST) Received: from spirit.jaded.net (unknown [209.82.45.200]) by enigma.trueimpact.net (Postfix) with ESMTP id 5829166B07; Mon, 7 Jan 2002 14:11:20 -0500 (EST) Received: (from dan@localhost) by spirit.jaded.net (8.11.6/8.11.6) id g07JBv401825; Mon, 7 Jan 2002 14:11:57 -0500 (EST) (envelope-from dan) Date: Mon, 7 Jan 2002 14:11:57 -0500 From: Dan Moschuk To: stable@freebsd.org Cc: phk@freebsd.org Subject: Hang in md driver Message-ID: <20020107141157.A1759@spirit.jaded.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I can reproduce a hang in the md driver reliably. Setup: dd if=/dev/zero of=image bs=32k count=8k vnconfig -s labels -c vn0 image diskabel -r -w vn0 auto newfs vn0c dd if=image of=/dev/md0 bs=32k count=8k mount /dev/md0c /mnt This works as expected. If I run bonnie against /mnt with a 64M filesize, everything is fine. However, once I up that size to 128M it will hang half way through. Using an mfs partition instead yields no problems. I've tested this against a 4.3 (512M ram) and a 4.4 (1.5GB ram) boxes respectively and both are affected. top says the bonnie process is in the "MD sec" state. Cheers, -Dan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message