From owner-freebsd-current Mon Feb 11 3:44:45 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 1F8B437B449; Mon, 11 Feb 2002 03:44:21 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id WAA28011; Mon, 11 Feb 2002 22:44:08 +1100 Date: Mon, 11 Feb 2002 22:46:58 +1100 (EST) From: Bruce Evans X-X-Sender: To: Mikhail Teterin Cc: , Subject: Re: panic: bdwrite: buffer is not busy In-Reply-To: <200202101008.g1AA8eX08143@aldan.algebra.com> Message-ID: <20020211224352.W682-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 On Sun, 10 Feb 2002, Mikhail Teterin wrote: > On 10 Feb, 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. > > Fdisk I don't really need, but attempting to newfs the floppy caused the > same panic :-\ And mounting the already formatted floppy leads to > "invalid argument". Could we have this fixed soon, please? The inability > to access a floppy is a great setback for my local FreeBSD advocacy > efforts :-) Newfs'ing /dev/fd0 (instead of /dev/fd0[a-c]) should work better. Not using devfs might work too. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message