From owner-freebsd-current Mon Feb 11 19:47:34 2002 Delivered-To: freebsd-current@freebsd.org Received: from newman2.bestweb.net (newman2.bestweb.net [209.94.102.67]) by hub.freebsd.org (Postfix) with ESMTP id 409A837B64F; Mon, 11 Feb 2002 18:19:09 -0800 (PST) Received: from okeeffe.bestweb.net (okeefe.bestweb.net [209.94.100.110]) by newman2.bestweb.net (Postfix) with ESMTP id A3986231A2; Mon, 11 Feb 2002 21:18:03 -0500 (EST) Received: by okeeffe.bestweb.net (Postfix, from userid 0) id 374C89F3C9; Mon, 11 Feb 2002 21:12:44 -0500 (EST) Date: Mon, 11 Feb 2002 22:46:58 +1100 (EST) From: Bruce Evans To: Mikhail Teterin Cc: , Subject: Re: panic: bdwrite: buffer is not busy Message-Id: <20020212021244.374C89F3C9@okeeffe.bestweb.net> 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message