From owner-freebsd-current Sat Feb 9 20:22:50 2002 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (faustus.neophilic.net [209.31.233.166]) by hub.freebsd.org (Postfix) with ESMTP id B7C3437B416; Sat, 9 Feb 2002 20:22:46 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id g1A4J6x32310; Sun, 10 Feb 2002 05:19:06 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Bruce Evans Cc: Julian Elischer , John Baldwin , Mikhail Teterin , current@FreeBSD.ORG Subject: Re: panic: bdwrite: buffer is not busy In-Reply-To: Your message of "Sun, 10 Feb 2002 14:30:42 +1100." <20020210142836.D6790-100000@gamplex.bde.org> Date: Sun, 10 Feb 2002 05:19:06 +0100 Message-ID: <32308.1013314746@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20020210142836.D6790-100000@gamplex.bde.org>, Bruce Evans writes: >On Sat, 9 Feb 2002, Julian Elischer wrote: > >> On Sun, 10 Feb 2002, Bruce Evans wrote: >> >> > >> > This is a well known bug in the device layer. I reported it on 2001/12/26 >> > and fixed it locally a little later. See the thread in -current about >> > "panic during fdisk'ing a md(4) device" for patches. >> > >> Can you commit the fix? > >The maintainer should be able to it better. I rarely test the devfs parts, >but the bulk of the patch is to help devfs. My patch needs some cleanups >(mainly non-hacked interfaces) anyway. The maintainer is busy rewriting that entire area of the code which will help immensely :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message